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 }}
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
I noticed that webpack builds of our project froze node without exiting if a JS error was encountered during the bundling. Manually calling process.exit() didn't work either. Debugging pointed towards node-sass being the culprit as the process exited when removing all scss imports from the webpack build. I've only been able to repro the issue when including most of the codebase, making it hard to create a minimal example.
Instead I found a similar issue with the same symptom with an example I was able to reproduce myself: nodejs/node#17872
First problem is that you never return from the importer properly. But even if you would do, it still hangs.
process.exit() is running while there are other things scheduled in the event loop. This is special with node-sass since we jump to native code and return to JavaScript as we need (for example for importers).
Implements equality for selector lists in a cleaner and more efficient manner.
Related issue: sass#2666 (likely fixed by this change but I haven't verified).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
npm -v
): 6.9.0node -v
): v12.1.0 and v10.15.3 testednode -p process.versions
):node -p process.platform
): darwin (Mac OS X 10.14.3)node -p process.arch
): x64node -p "require('node-sass').info"
):npm ls node-sass
):I noticed that webpack builds of our project froze node without exiting if a JS error was encountered during the bundling. Manually calling
process.exit()
didn't work either. Debugging pointed towards node-sass being the culprit as the process exited when removing all scss imports from the webpack build. I've only been able to repro the issue when including most of the codebase, making it hard to create a minimal example.Instead I found a similar issue with the same symptom with an example I was able to reproduce myself: nodejs/node#17872
Updated reproducible minimal example that should work with both node v12.1.0 and v10.*.
Help much appreciated!
The text was updated successfully, but these errors were encountered: