-
Notifications
You must be signed in to change notification settings - Fork 809
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.extract()
causing the resources processing to freeze with 95% emitting
message
#925
Comments
I was getting the same thing. I removed my package-lock.json file and ran npm install again. It was fine. Try that otherwise repeat the same as above except in your package.json change laravel-mix version 0.* |
Same issue here. Keeps freezing on Windows 10 with latest Laravel-mix version.. |
UPDATE: I've upgraded the And it doesn't matter if you install the packages with |
Got the same issue but with |
|
Hi @PascaleBeier, Thanks for your suggestion but it doesn't work for me. |
I use Laravel Mix also for non-Laravel projects where is no So, yes, @PascaleBeier is [almost] right, you should set mix
.options({
publicPath: 'public'
}) |
Unfortunately, it doesn't solve my issue. I'm using fresh laravel installation ( @taai, i tried your solution but with no success : const { mix } = require('laravel-mix');
mix.options({
processCssUrls: false,
publicPath: 'public'
});
mix.sass('resources/assets/sass/app.scss', 'public/css');
mix.autoload({
jquery: ['$', 'window.jQuery', 'jQuery']
});
mix.js('resources/assets/js/app.js', 'public/js');
mix.extract([
'axios', 'vue', 'jquery', 'bootstrap-sass',
], '/assets/js/vendors.js'); |
@arcanedev-maroc Easy! The cause of the problem is the same – wrong paths! In this case, you are starting the path with a slash ( If you wanted to extract mix.extract([
'axios', 'vue', 'jquery', 'bootstrap-sass',
], 'public/assets/js/vendors.js'); @JeffreyWay , maybe you could make Laravel Mix to check if the disk drive exists? Because nobody can guess that |
OMG @taai, you're a lifesaver 🙌 I've changed the code to this and it WORKS!!! const { mix } = require('laravel-mix');
mix.options({
processCssUrls: false,
publicPath: 'public'
});
mix.sass('resources/assets/sass/app.scss', 'public/assets/css');
mix.autoload({
jquery: ['$', 'window.jQuery', 'jQuery']
});
mix.js('resources/assets/js/app.js', 'public/assets/js');
mix.extract([
'axios', 'vue', 'jquery', 'bootstrap-sass',
], 'public/assets/js/vendors.js'); @JeffreyWay, i don't know if it's a bug or an attendant behavior. But it's definitely a breaking change (Or only for Windows users ?) when you upgrade from laravel-mix |
Based on the documentation, the filenames are automatically done for you. Not sure if specifying a filename, which in this case, the same filename does affect it or not. |
Can someone please test this again? It is failing on my windows 10 system as well. |
@taai thank you for that, I was also using W10 and laravel-mix for a non Laravel project and |
Putting
in webpack.mix.js worked just fine thanks. |
i'm not sure but this might be because you've changed the artisan file name. |
I had the same issue and fixed by removing "/" from the beginning of the second arg |
npm list --depth=0
)node -v
): 6.10.3npm -v
): 5.0.3Description:
Hi artisans,
Can anybody confirm this (Especially on Windows) or am i the only one who have this issue !!
Steps To Reproduce:
Start with a new laravel installation
Edit the webpack.mix.js file like this
After that run:
npm run dev
And if you comment the
mix.extract([...], '/assets/js/vendors.js');
, the build pass !!Also, i want to point something weird with
mix-manifest.json
:I think the first line
"/d:/assets/js/vendors.js": "/d:/assets/js/vendors.js",
is invalid because it starts with/d:/assets
!!The text was updated successfully, but these errors were encountered: