Turbopack does not support imports from stream/consumers

[paulbrimicombe]

Link to the code that reproduces this issue

https://github.com/paulbrimicombe/nextjs-stream-consumers-bug?target=https://github.com

To Reproduce

1. Install dependencies: npm install
2. Attempt to build the code using Turbopack: npm run build — the error Module not found: Can't resolve 'stream/consumers' will be displayed
3. Attempt to build the code using Webpack: npm run build -- --webpack — no errors will be shown
4. Update the code in page.tsx to add the node: prefix to the stream/consumers import
5. Attempt to build the code using Turbopack: npm run build — the error Cannot find module 'node:stream/consumers': Unsupported external type Url for commonjs reference will be displayed

Current vs. Expected behavior

• Utility consumer functions should be able to be imported without the node: prefix (like other Node.js libraries).
• These functions should be able to be imported in CommonJS code

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Wed Nov  5 21:30:44 PST 2025; root:xnu-11417.140.69.705.2~1/RELEASE_ARM64_T6041
  Available memory (MB): 24576
  Available CPU cores: 14
Binaries:
  Node: 22.21.1
  npm: 11.10.0
  Yarn: 1.22.22
  pnpm: 10.28.0
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

A quick search of the Turbopack codebase for similar Node.js libraries such as stream/promises or stream/web indicates that there is some missing handling for stream/consumers.

[Joshualover]

Great bug report! 👍

Thanks for the detailed reproduction steps and environment information.

Quick suggestion:

Since this is a Turbopack issue, you might want to check if the fix is already in the latest Turbopack version:

npm update next

If the issue persists, you could also try:

1. Using the --webpack flag instead of Turbopack
2. Opening an issue in the Turbopack repository directly

Would be happy to help test or provide more suggestions!

[paulbrimicombe]

Thanks for the comment @Joshualover

Using the --webpack flag instead of Turbopack

This is our current workaround but it's not ideal (not least because the default is now Turbopack)

npm update next

This has no effect on the bug — this reproduction uses all of the latest package versions

Opening an issue in the Turbopack repository directly

Um, isn't the Turbopack source code in this repository — at https://github.com/vercel/next.js/tree/canary/turbopack/crates?target=https://github.com ? Which other repository are you expecting this to be raised in?

[mischnic]

Will be fixed by #90819

Opening an issue in the Turbopack repository directly

That is wrong. This is the right reposity, the code is in crates and turbopack/crates as you said.