Skip to content
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

Move all NPM modules into a single chunk in dev mode. #1505

Merged
merged 1 commit into from
Mar 25, 2017

Conversation

arunoda
Copy link
Contributor

@arunoda arunoda commented Mar 25, 2017

Closes #941

This will isolate all the NPM modules into a single chunk.
That chunk won't touch by webpack unless, there's a new NPM module.
That gives us much better re-build performance.

This does the same think as what #941 does. But now this is automatically works for all NPM modules.

This will isolate all the NPM modules into a single chunk.
That chunk won't touch by webpack unless, there's a new NPM module.
That gives us much better re-build performance.
@sergiodxa
Copy link
Contributor

Did this include every module inside node_modules? What about non required modules? If I have ESLint inside my node_modules this include that too?

@arunoda
Copy link
Contributor Author

arunoda commented Mar 25, 2017

@sergiodxa ah not all.
But all of the modules which used in the client app and sees by Webpack.

@rauchg rauchg merged commit a879f47 into vercel:master Mar 25, 2017
@sergiodxa
Copy link
Contributor

@arunoda ahh ok, I just wanted to understand that

@arunoda arunoda deleted the add-vendor-chunk branch March 26, 2017 00:58
rauchg added a commit that referenced this pull request Mar 26, 2017
@arunoda arunoda restored the add-vendor-chunk branch March 26, 2017 19:31
@arunoda arunoda deleted the add-vendor-chunk branch March 26, 2017 20:59
@frol
Copy link
Contributor

frol commented Apr 5, 2017

@rauchg Why was it reverted? Will it be improved somehow?

@arunoda
Copy link
Contributor Author

arunoda commented Apr 6, 2017

@frol we did another PR with the same. This one had a bug.

@frol
Copy link
Contributor

frol commented Apr 6, 2017

It would have been much helpful if you refer to the issues/PRs. It seems that that was #1512. Thank you.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants