-
Notifications
You must be signed in to change notification settings - Fork 203
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
Module not found can't resolve 'fs' in node_modules\tempa-xlsx #168
Comments
@Srivastava295 Thanks! |
I'm having this problem too. I made the build work by adding this lines to the 'resolve' field of webpack.config.js file (which is located in node_modules/react-scripts/config):
Of course, this is a temporary fix. The problem can be fixed definitively by replacing tempa-xlsx with xlsx in the package's source code. I'll try to make a pull request fixing it soon. |
Any updates for the fix? Also will I be able to export if I add the above code? |
I guess the package is not being maintained anymore. If you add the above code, it will work as long as you don't cause your |
used this package somtimes last year and it worked, @bryancalisto your fix doesnt seems to be working anymore. any help, |
Any updates? |
I switched from NPM to YARN and everything works perfectly. NPM has a lot of problems, try switching to YARN if you can. Maybe it can solve your problem |
Installing the xlsx package fixes it npm i xlsx |
Hi guy, any fix on this bug yet? |
Adding |
@alkanpolat comment resolve my issue. |
i try all above solution still facing same issue |
resolve my issue. |
I added the following dependencies to package.json: "react-data-export": "^0.6.0" After that, I ran these commands in order: bash "tempa-xlsx": "0.0.1" |
We tried updating react-scripts from 4.0.3 to 5.0.0 with react-data-export 0.6.0 and xlsx 0.17.2, and when we try to build it fails with the error
Module not found: Error: Can't resolve 'fs' in react-data-export\node_modules\tempa-xlsx
What fix needs to be applied to maintain react-scripts version 5.0.0? Thanks!
The text was updated successfully, but these errors were encountered: