-
-
Notifications
You must be signed in to change notification settings - Fork 27.2k
Improve vendor chunk names in development #9569
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
|
@iansu @mrmckeb @ianschmitz @petetnt I know you probably have a ton of stuff to review right now, but this is a 1-line change that shouldn't take a lot of thought. Can you take a look? |
|
I'm not opposed to this, any thoughts @ianschmitz or @iansu? |
|
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
|
Bump! I still want this one-line change. |
f03bbf9 to
8432ce1
Compare
8432ce1 to
81ea7ad
Compare
|
Good idea @jrr. Seems like a good quality of life improvement. Thanks! |
Out of the box today, CRA produces numbered vendor chunks. They look like this in production:
And like this in development:
This is a good default for production, following webpack's guidance (
splitChunks.name: false) to create stable, cacheable names.In development, though, when I'm trying to understand exactly what code is delivered when, I'd like to know more about what goes in to those chunks.
This PR sets
splitChunks.nametotruein development, producing vendor chunk names like this:Is this something others would be interested in?
Related issues:
#4769
#6155
#6240