crypto-browserify takes up the majority of next bundle size

[mcmxcdev]

Describe the feature you'd like to request

crypto-browserify didn't have new commits since 2018.

It takes up quite a chunk according to: https://bundlephobia.com/package/crypto-browserify@3.12.0

Also visible as part of @next/bundle-analyzer:

Describe the solution you'd like

Switch to an alternative, maintain a fork or drop it altogether.

Describe alternatives you've considered

/

[balazsorban44]

You are likely using a library that imports crypto even if it's targeted for browsers. Next.js falls back to a polyfill for historical reasons.

You can now opt out of this behavior by setting the experimental.fallbackNodePolyfills: false option in your next.config.js but you'll have to make sure the library or your code does not unnecessarily import crypto then. Read more at #39248

[mcmxcdev]

Hey Balasz, thanks for the detailed explanation, I really appreciate it!

Looks like I will have to wait for v12.2.6 to drop to try it out but looks promising ;)

[balazsorban44]

You can test it out on next@canary already, or wait for the next latest release, of course. 👍

[github-actions]

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.