Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't resolve fs in 3.11.0 filestack-js\build\module\lib\api\upload #319

Closed
Cherry opened this issue Jan 15, 2020 · 10 comments
Closed

Can't resolve fs in 3.11.0 filestack-js\build\module\lib\api\upload #319

Cherry opened this issue Jan 15, 2020 · 10 comments
Assignees

Comments

@Cherry
Copy link

Cherry commented Jan 15, 2020

After 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.

@reubenharcourt
Copy link

Same error and fix here

@DmitriyGribennikov
Copy link

have the same error today

@pcholuj
Copy link
Contributor

pcholuj commented Jan 16, 2020

Hi
Sorry we are working to resolve this issue. For now please use previous version of filestack-js.

@pcholuj pcholuj self-assigned this Jan 16, 2020
@noisy
Copy link

noisy commented Jan 20, 2020

it looks like downgrade to 3.10.1 is not enough.

v3.10.0...master

For me downgrade to "3.10.0" resolved the issue.

@Cherry
Copy link
Author

Cherry commented Jan 23, 2020

Just to confirm, upgrading to the newest release, 3.11.1, still seems to have the issue.

@kennysliding
Copy link

I have run into the same issue when building the webpack too. Can you guys share the version number which has no "fs" error? Thanks.

@Cherry
Copy link
Author

Cherry commented Jan 23, 2020

I have run into the same issue when building the webpack too. Can you guys share the version number which has no "fs" error? Thanks.

3.10.1 is the latest version that works for us, though some have reported having to downgrade to 3.10.0.

@frogamic
Copy link

I have also encountered this issue, rolling back to 3.10.1 worked for me.

@pcholuj
Copy link
Contributor

pcholuj commented Jan 24, 2020

Hi, sorry there was a problem with local linking package. new Release 3.11.2 should fix the problem. Tested with webpack. @Cherry can you confirm?

@Cherry
Copy link
Author

Cherry commented Jan 24, 2020

I can confirm 3.11.2 is working fine for us now. Thanks @pcholuj!

@maryfs maryfs closed this as completed Jan 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants