uppy/examples/custom-provider
Mikael Finstad 415681f659
Use cors module instead of custom cors logic (#2823)
* use cors module instead of custom cors logic #2762

- adds support for regex COMPANION_CLIENT_ORIGINS_REGEX
- encapsulate custom cors header merge logic in own middleware
- pull out non cors logic from middleware
- unit test the cors middleware

* fix capitalization

Co-authored-by: Julian Gruber <julian@juliangruber.com>

Co-authored-by: Julian Gruber <julian@juliangruber.com>
2021-03-26 19:38:23 +00:00
..
client Update Linter (#2796) 2021-03-15 16:25:17 +00:00
output add custom provider example 2018-04-09 23:12:41 +01:00
server Use cors module instead of custom cors logic (#2823) 2021-03-26 19:38:23 +00:00
.gitignore add custom provider example 2018-04-09 23:12:41 +01:00
babel.config.js Update Linter (#2796) 2021-03-15 16:25:17 +00:00
index.html add custom provider example 2018-04-09 23:12:41 +01:00
package-lock.json build(deps): bump elliptic from 6.5.2 to 6.5.4 (#2794) 2021-03-08 18:16:49 +00:00
package.json error on import lint failure + some misc lint fixes (#2813) 2021-03-20 11:02:49 +01:00
readme.md examples: document npm run build, closes #2024 2020-03-30 16:07:24 +02:00

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

To run this example, make sure you've correctly installed the repository root:

npm install
npm run build

That will also install the dependencies for this example.

Then, again in the repository root, start this example by doing:

npm run example custom-provider