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
mix.sass() stopped working after upgrade to webpack v4 #1870
Comments
Hmm, okay. You're not the first to report this, but I've been having trouble reproducing it on my own. What would help me most is if someone could give me exact steps to reproduce the problem. |
I experienced the same issue. Not working Works |
@JeffreyWay i've also tried to remove @bjora857 that might be the issue, i've import calls all over the place, but am not sure how the dynamic-import is effecting the sass build 😢 |
Getting the same issue on another project. On yet another my CSS file is completely empty instead:
|
If you check the Mix 4 release notes, we mention that there are issues related to dynamic imports and CSS extraction. I'm not sure that this is something we can fix until webpack 5 comes out. |
@JeffreyWay yeah i saw it but why the sass build is being affected by the dynamic imports ? |
@ctf0 |
If your project uses dynamic imports, I'd recommend holding off until webpack is upgraded to v5 early next year. Once they do, we can fix this issue very quickly. Until then, my hands are tied. |
Is there a reason behind sticking with
Pretty sure this is relates (duplicate) of #1856 |
Closing this, as there's nothing we can do until webpack 5. |
I have the same issue, I don't have any css in my components. I only use |
Can confirm, removing conditional chunk import resolved the issues for mix.sass(). I've noticed that this only happens if you use conditional chunk import with mix.extract() and works properly without extraction too. |
@OksanaRomaniv I have the same issue and your solution worked, but have you gotten any other fix to get it working while using |
@victorybiz, Unfortunately, no. Couldn't make it work together. I do think that that's a bug and should be addressed by Laravel Mix devs. |
Can confirm this issue still exists in Laravel Mix v5 Does anyone know a workaround on this? I don't wanna stay on Laravel Mix v2 forever lol Lararvel v6.12.0 Packages
webpack.mix.js
Output
|
exactly same issue here! |
possible workaround with the sass the js will still generate n.js though |
Have spend alot of time trying to solve this... |
I have the same issue with Laravel 8 and "laravel-mix": "^5.0.1" I was able to compile the app.scss file by adding at the end the file looks like that: I hope it helps! |
node -v
): v10.9.0npm -v
): v6.4.1Description:
mix.sass()
stopped working and now in every compiled css file am gettingSteps To Reproduce:
webpack.mix.js
The text was updated successfully, but these errors were encountered: