-
-
Notifications
You must be signed in to change notification settings - Fork 430
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
Remove synchronous compilation #333
Comments
Can I recommend NOT removing this feature just yet. There are clearly some bugs in node-sass/libsass when loading sass from more than one entry point (or even two webpack builds in a single process) using the async callback. With even moderately complex sass files (bootstrap-sass) trying to use two entry points results in random |
Can confirm @gcarothers |
Strange. I do have multiple entry points and I never experienced this I'm thinking of moving node-sass into a separate process. Do you think this might solve it? |
I'd be happy to test it, maybe a separate branch? In the mean time, I'm going to use a parallel shell script to compile all the SASS into intermediate CSS and then webpack those. I'll report back to see if that works better. |
sass/node-sass#1669 seems to be the root cause (changes to how node sass did memory management) hopefully node-sass will resolve soon. Until then downgrading back to older node-sass solves the stack level too deep errors completely. |
Using the PS thank you @gcarothers I'll probably just downgrade to 3.x for the time being. |
Having issues with bootstrap 4 compilation.
|
We currently have two code paths: one for synchronous compilation and one for asynchronous compilation. Since we learned that synchronous compilation can seriously slow down your build speed, we already discouraged the use of enhanced-require. In the next major release, we will completely remove the synchronous code path since it is a lot of work to maintain this second code path.
The text was updated successfully, but these errors were encountered: