Can't resolve `fs` in 3.11.0 `filestack-js\build\module\lib\api\upload`
See original GitHub issueAfter updating to the latest version, our webpack build is failing with:
Module not found: Error: Can't resolve 'fs' in '...\node_modules\filestack-js\build\module\lib\api\upload'
Downgrading to 3.10.1 resolves the issue.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Module not found: Error: Can't resolve 'fs' in - Stack Overflow
js Module not found: Error: Can't resolve 'fs' in 'C:\Source\nien\vital10-frontend\node_modules\tslint\lib' i 「wdm」: Failed to compile.
Read more >Can't resolve fs - Help Requests - The Aurelia Discourse
I am running into an error that I have not seen before in all my testing and compiling of Aurelia using webpack and...
Read more >filestack-js - npm
The Filestack Picker - an upload widget for the web that integrates over a dozen cloud providers and provides pre-upload image editing.
Read more >Module not found: Can't resolve 'fs' error [Solved] | bobbyhadz
The error "Module not found: Error: Can't resolve 'fs'" occurs because there has been a breaking change in Webpack version 5.
Read more >Can't resolve 'fs' in '/home/username/project-directory/src'
Is there a node module I can install to deal with local files? I'd like to be able to have the user open...
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 FreeTop 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
Top GitHub Comments
it looks like downgrade to 3.10.1 is not enough.
https://github.com/filestack/filestack-js/compare/v3.10.0...master
For me downgrade to
"3.10.0"
resolved the issue.Just to confirm, upgrading to the newest release,
3.11.1
, still seems to have the issue.