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

Significant bundle size increase in Nextjs 13.3.3 #42813

Closed
1 task done
belgattitude opened this issue Nov 11, 2022 · 4 comments
Closed
1 task done

Significant bundle size increase in Nextjs 13.3.3 #42813

belgattitude opened this issue Nov 11, 2022 · 4 comments
Labels
bug Issue was opened via the bug report template.

Comments

@belgattitude
Copy link
Contributor

belgattitude commented Nov 11, 2022

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022
Binaries:
  Node: 16.17.0
  npm: 8.19.3
  Yarn: 4.0.0-rc.28
  pnpm: 7.15.0
Relevant packages:
  next: 13.0.3
  eslint-config-next: 13.0.3
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

There's a significant size increase when upgrading from 13.3.2 to 13.3.2.

"Shared by all" went from 150kb to 180kb (swc complier and swcMinify: true)

image

"Pages" sees a size increase

image

"Bundle analyzer" report a size increase in "parsed size"

image

Expected Behavior

A size increase can happen but as this one is quite big, I guess it should be taken into consideration.

Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

belgattitude/nextjs-monorepo-example#2896

To Reproduce

Follow the instructions in the PR: belgattitude/nextjs-monorepo-example#2896.

You'll find how to install both version to easily compare locally.

@belgattitude belgattitude added the bug Issue was opened via the bug report template. label Nov 11, 2022
@belgattitude
Copy link
Contributor Author

belgattitude commented Nov 11, 2022

Disabling swcMinify helped to get back to expected sizes. Gentle ping to @kdy1

See also #30237 (comment)

@kdy1
Copy link
Member

kdy1 commented Nov 11, 2022

Fixed by #42790

@kdy1 kdy1 closed this as completed Nov 11, 2022
@belgattitude
Copy link
Contributor Author

belgattitude commented Nov 11, 2022

Great, thanks a lot, I'll try the next canary

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants