Part of the dev-dependency major-version upgrades. These required code changes so they're split out from the no-code-change batch (#6315). **AI Disclaimer** : AI Used - **glob 8 → 13** — `@uppy/locales` scripts: the callback API was removed, so `getPaths()` uses the promise form and `test.mjs` uses the named `globSync`. - **npm-packlist 5 → 11** — `upload-to-cdn.js`: v7+ takes an `@npmcli/arborist` tree instead of `{ path }`; loads the tree and passes it to `packlist()`. Adds `@npmcli/arborist` as a devDependency. - **nock 13 → 14** (`@uppy/companion`) — the v14 @mswjs/interceptors rewrite crashed the SSRF tests in `http-agent.test.ts`; nock interception is now kept off by default and only activated for the one test that mocks a host. - **@types/use-sync-external-store 0 → 1** — `@uppy/react`: v1's exports map only exposes extensionless subpaths, so imports use `use-sync-external-store/shim` and `/with-selector` (runtime supports both). |
||
|---|---|---|
| .. | ||
| __mocks__ | ||
| infra/kube | ||
| output | ||
| src | ||
| test | ||
| .gitignore | ||
| .npmignore | ||
| ARCHITECTURE.md | ||
| CHANGELOG.md | ||
| env_example | ||
| heroku.yml | ||
| KUBERNETES.md | ||
| LICENSE | ||
| Makefile | ||
| nodemon.json | ||
| package.json | ||
| README.md | ||
| start-dev | ||
| tsconfig.build.json | ||
| tsconfig.json | ||
| tsconfig.shared.json | ||
| vitest.config.ts | ||
Companion
Companion is a server integration for Uppy file uploader.
It handles the server-to-server communication between your server and file storage providers such as Google Drive, Dropbox, etc. Companion is not a target to upload files to. For this, use a https://tus.io server (if you want resumable) or your existing Apache/Nginx server (if you don’t). See here for full documentation
Install
npm install @uppy/companion
If you don’t have a Node.js project with a package.json you might want to
install/run Companion globally like so:
[sudo] npm install -g @uppy/companion@1.x (best check the actual latest
version, and use that, so (re)installs are reproducible, and upgrades
intentional).
Usage
companion may either be used as pluggable express app, which you plug to your existing server, or it may also be run as a standalone server:
Plug to an existing server
import express from 'express'
import bodyParser from 'body-parser'
import session from 'express-session'
import companion from '@uppy/companion'
const app = express()
app.use(bodyParser.json())
app.use(session({ secret: 'some secrety secret' }))
// ...
// be sure to place this anywhere after app.use(bodyParser.json()) and app.use(session({...})
const options = {
providerOptions: {
drive: {
key: 'GOOGLE_KEY',
secret: 'GOOGLE_SECRET',
},
},
server: {
host: 'localhost:3020',
protocol: 'http',
},
filePath: '/path/to/folder/',
}
const { app: companionApp } = companion.app(options)
app.use(companionApp)
To enable companion socket for realtime feed to the client while upload is going
on, you call the socket method like so.
// ...
const server = app.listen(PORT)
// Pass the same `options` object you passed to `companion.app(options)` —
// `companion.socket` needs `options.server` to compute the external base path
// for incoming WS URLs (important behind reverse proxies).
companion.socket(server, options)
Run as standalone server
Please make sure that the required env variables are set before runnning/using companion as a standalone server. See.
$ companion
If you cloned the repo from GitHub and want to run it as a standalone server, you may also run the following command from within its directory
npm start
Deploy to heroku
Companion can also be deployed to Heroku
mkdir uppy-companion && cd uppy-companion
git init
echo 'export COMPANION_PORT=$PORT' > .profile
echo 'node_modules' > .gitignore
echo '{
"name": "uppy-companion",
"version": "1.0.0",
"scripts": {
"start": "companion"
},
"dependencies": {
"@uppy/companion": "latest"
}
}' > package.json
npm i
git add . && git commit -am 'first commit'
heroku create
git push heroku master
Make sure you set the required environment variables.