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

Config - Document splitChunks and minimize #1812

Closed
itsMapleLeaf opened this issue Feb 2, 2018 · 5 comments
Closed

Config - Document splitChunks and minimize #1812

itsMapleLeaf opened this issue Feb 2, 2018 · 5 comments

Comments

@itsMapleLeaf
Copy link

For webpack/webpack#6416: include links to config.optimize.splitChunks and config.optimize.minimize when the relevant docs are merged.

@skipjack skipjack changed the title Add links to removed plugin error Config - Document splitChunks and minimize Feb 3, 2018
@skipjack
Copy link
Collaborator

skipjack commented Feb 3, 2018

Can you submit a PR directed at the next branch to resolve this? BTW, the other v4 changes are tracked in #1706 so I may add this as a comment there. We won't merge next into master until v4 is actually released, otherwise we'd get a bunch of reports of missing features. But, if you submit the PR to next, these docs would be there as soon as it is merged. You could even link directly to the next branch in the meantime.

cc @TheLarkInn

@jeremenichelli
Copy link
Member

@kingdaro are you working on this? If not I can take care of it :)

@itsMapleLeaf
Copy link
Author

@jeremenichelli Go for it, I'm busy.

@jeremenichelli jeremenichelli self-assigned this Feb 27, 2018
@jeremenichelli
Copy link
Member

jeremenichelli commented Feb 27, 2018

Here's the PR for SplitChunks: #1863

I think minimize should be handle in a new PR and issue.

@jeremenichelli
Copy link
Member

Closing since we have an issue for optimization section and we already merged splitChunks docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants