-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
fix(webpack): avoid grouping with default name #7808
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
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #7808 +/- ##
==========================================
+ Coverage 68.86% 68.89% +0.02%
==========================================
Files 90 90
Lines 3835 3835
Branches 1037 1037
==========================================
+ Hits 2641 2642 +1
+ Misses 970 969 -1
Partials 224 224
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
I did a bunch of tests to ensure this fix is not causing dot file issue and webpack's default |
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.
Do we have an exmaple about what the new output dirs and files would be ?
For #7795 reproduction:
With a vendor shared between two pages:
Bud sadly (or happily :D) no simple reproduction for dotfile issue happened in previous releases |
I have projects that can replicate both issues so will test. EDIT: this solves both problems for me (both dotfile prefixed JS files and #7795). |
Will test it tomorrow! |
Just tested it with nuxt-next in two of our applications that were affected by the . bug before. Looks good to me! Everything seems to work! |
Update
|
Types of changes
Description
Fixes #7795 by letting webpack to use computed cache group key.
Related:
Checklist: