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

Massive bundle with next export #2005

Closed
craigmulligan opened this issue May 18, 2017 · 2 comments
Closed

Massive bundle with next export #2005

craigmulligan opened this issue May 18, 2017 · 2 comments

Comments

@craigmulligan
Copy link

Hey, I've been using #1576 fork for a little using next export. And with that approach it my app.js bundle was 140kb.

With the the v3-beta it's outputting a 1.2mb bundle.

I've checked webpack isn't running in dev mode during the build, but wondering if you have ideas on what might be happening?

@davscro
Copy link
Contributor

davscro commented May 18, 2017

Put webpack-bundle-analyzer into your project and check is there any suspicious module which shouldn't be there. Take a look at example below:
https://github.com/zeit/next.js/tree/v3-beta/examples/with-webpack-bundle-analyzer

@craigmulligan
Copy link
Author

Thanks for the pointer! It was actually an issue with a local mono-repo managed by Lerna, still not exactly sure why it's so bloated but must have something to do with the linking.

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

No branches or pull requests

2 participants