Could not install from "node_modules/@uppy/aws-s3"
See original GitHub issueEdit by @goto-bus-stop: This should be SOLVED in Uppy 1.9.1. Please ensure you have the latest versions by doing
npm install uppy@latest
if you are using theuppy
package, or for each plugin by doingnpm install @uppy/PLUGINNAME@latest
if you are using individual plugin packages.
what happen with the new version?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
@uppy/aws-s3 - npm
Start using @uppy/aws-s3 in your project by running `npm i @uppy/aws-s3`. There are 33 other projects in the npm registry using @uppy/aws-s3.
Read more >Help with Uppy + AWS S3 Example · Issue #1116 - GitHub
I am trying to get the example to work for uppy to work with S3 using a presigned url. Can anybody help explain...
Read more >AWS S3 - Uppy
The @uppy/aws-s3 plugin can be used to upload files directly to an S3 bucket. Uploads can be signed using either Companion or a...
Read more >Is there a way to "npm install" from AWS S3? - Stack Overflow
According to the documentation, you should be able to install a package from any url resolving to a gzipped tarball.
Read more >Uppy AWS S3 Plugin - Filebase
Uppy features a comprehensible API and a variety of modules and plugins for file manipulation and management. Uppy currently does not support Windows...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@arturi just published 1.9.1 which appears to fix the issue:
Thanks all for notifying us!
@zifahm for now, I stick with older version in the lock file (@uppy/core v1.7.1) … don’t delete the lock file, otherwise
^1.7.1
will resolve to 1.8, then it’ll error. Or you have to pin the exeact version and do not use^