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
Fix bug: extractVueStyles not using specified file #1467
Fix bug: extractVueStyles not using specified file #1467
Conversation
Fixes laravel-mix#1460 Before the fix, we would recycle an existing extract plugin without assigning the custom extraction filename. This is now fixed.
@@ -261,28 +261,28 @@ module.exports = function() { | |||
options: Config.babel() | |||
}, | |||
|
|||
scss: vueExtractPlugin.extract({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this didn't crash before, because vueExtractPlugin would have been undefined if Config.extractVueStyles
evaluated to false…
@JeffreyWay We confirm an issue which this pull request will resolve. Tested locally, looks good. |
Thanks! :) |
@JeffreyWay When will this PR be in a release? |
Next week. |
@JeffreyWay ETA on this? Really waiting hard for this fix. |
@vyuldashev It's now tagged in v2.1. |
@JeffreyWay This breaks unfortunately.
|
Yeah, confirmed. Fixing this now, and will tag. |
Okay, done. Patched in 2.1.2. |
Thanks! It's back to the old situation now :) |
Fixes #1460
Before the fix, we would recycle an existing extract plugin without assigning the custom extraction filename.
This is now fixed.
Please note that PR #1466 needs to be updated after merging this PR, because it extracted the rules into dedicated files and I doubt that git is smart enough to merge these changes.