mirror of
https://github.com/transloadit/uppy.git
synced 2026-07-23 02:08:30 +00:00
eb8a806908
* fix uploadRemoteFile undefined for some reason, only when testing locally using VITE_COMPANION_URL=https://api2.transloadit.com/companion only we get this error... i'm thinking for some reason, the remote file gets serialized into state and then de-serialized again causing remote.requestClient to be gone so I solve it by instead storing the request clients in Uppy fixes #4791 * fix bugs * remove unrelated space changes * apply suggestions * Update Uppy.js * fix lint --------- Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> |
||
|---|---|---|
| .. | ||
| client | ||
| server | ||
| index.html | ||
| package.json | ||
| README.md | ||
Uppy + Companion + Custom Provider Example
This example uses @uppy/companion with a dummy custom provider. This serves as an illustration on how integrating custom providers would work
Run it
Note: this example is using fetch, which is only available on Node.js 18+.
First, you want to set up your environment variable. You can copy the content of
.env.example and save it in a file named .env. You can modify in there all
the information needed for the app to work that should not be committed
(Google keys, Unsplash keys, etc.).
[ -f .env ] || cp .env.example .env
To run the example, from the root directory of this repo, run the following commands:
corepack yarn install
corepack yarn build
corepack yarn workspace @uppy-example/custom-provider start