You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Can't resolve 'fs' in '.\node_modules\css\lib\stringify' when building #139
I'm getting this error trying to use a dependent package in the browser. Please can you try / catch loading of fs? Then it'll be fine as long as we don't need sourcemap support (which I don't!)
I worked on removing the source-map support. This will solve the issue. Trying to reach out to the rework members before going into the fork route (and discussing with my company for the PR route).
ref: #164
Activity
praveen0202-zz commentedon Jul 1, 2020
Im also facing same issue
jkeen commentedon Jul 21, 2020
Looks like it works in Node 10.x, but not 12.x+Haven't tested 11.xEDIT: nevermind, I'm also having this problem.
satelllte commentedon Jul 27, 2020
Having the same issue on
css@3.0.0FatalIdiot commentedon Aug 18, 2020
Seems like "fs" package is no longer present in NPM and when trying to install it just downloads README and package.json files, no actual package.
flyFatSeal commentedon Sep 4, 2020
Can anyone help?
YunFeng0817 commentedon Sep 9, 2020
add the following code to the webpack.config.js
It works for me.
issue reworkcss#139 catch error if `fs` module not found - as when ru…
IanGrainger commentedon Oct 25, 2020
I'm getting this error trying to use a dependent package in the browser. Please can you
try / catchloading offs? Then it'll be fine as long as we don't need sourcemap support (which I don't!)PR here: #146
Fi1osof commentedon Dec 8, 2020
Possible solution: #146 (comment)
holblin commentedon May 26, 2022
I worked on removing the source-map support. This will solve the issue. Trying to reach out to the rework members before going into the fork route (and discussing with my company for the PR route).
ref: #164