node browser modules expected?

[greggb]

I'm trying to audit the bundle sizes in my project, and I can't explain where some of these modules are coming from. Are they required by next.js in general, or am I triggering their inclusion somehow when using next/link or next/router? I'd be interested in trying an alternative approach in my code if there's something I'm doing to include these large-ish packages.

The big standouts for me are

• stream-browserify
• buffer
• readable-stream
• html-tokenize

[timneutkens]

Those are all included through some npm library you're importing, they're not used in Next.js.

[greggb]

Thanks @timneutkens Any idea why I'd see this output for yarn why?

➜ yarn why stream-browserify
yarn why v1.22.5
[1/4] 🤔  Why do we have the module "stream-browserify"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "[email protected]"
info Reasons this module exists
   - "next" depends on it
   - Hoisted from "next#stream-browserify"
info Disk size without dependencies: "292KB"
info Disk size with unique dependencies: "532KB"
info Disk size with transitive dependencies: "772KB"
info Number of shared dependencies: 7
✨  Done in 0.58s.

[timneutkens]

Because it's part of the stream polyfilling. It's only included when stream is used by a dependency