Module not found: Error: Can't resolve 'stream/web'

[ctq123]

Reproduction

Module not found: Error: Can't resolve 'stream/web' in '/Users/alan/project/duapp/vscode/packages/du-i18n/node_modules/fetch-blob'

Steps to reproduce the behavior:

1. yarn
2. yarn start
3. start fail

Expected behavior

start success

Screenshots

Your Environment
vscode extension development

software	version
node-fetch	3.0.0
node	v14.17.3
npm	6.14.13
Operating System	macos

Additional context

[ctq123]

[jimmywarting]

don't get why u recive a error. it's wrapped around a try/catch

[LinusU]

@ctq123 I believe that this is only a warning right? When WebPack detects an import inside try/catch it just prints a warning, the bundle should still be okay to use...

[btakita]

Running sapper, rollup, on AWS Lambda with version nodejs14.x.

I'm getting the error:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'stream' imported from /path/to/apps/web/server2.js
    at packageResolve (internal/modules/esm/resolve.js:664:9)
    at moduleResolve (internal/modules/esm/resolve.js:705:18)
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:819:11)
    at Loader.resolve (internal/modules/esm/loader.js:89:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:73:40)
    at link (internal/modules/esm/module_job.js:72:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Rollup treats 'stream/web' as an external & hoists the require to the top of the js payload file.

The output looks something like this:

import require$$0 from 'stream/web';
// ...
if (!globalThis.ReadableStream) {
  try {
    Object.assign(globalThis, require$$0);
  } catch (error) {
		// TODO: Remove when only supporting node >= 16.5.0
    Object.assign(globalThis, ponyfill_es2018.exports);
  }
}

[jimmywarting]

Hmm, i did not account for bundlers to hoist stuff like this. This kind of conditional import should really be converted to top level await + async import to match the same behavior...
Should report/suggest it to rollup

[wood1986]

webpack should add stream/web to NodeTargetPlugin. See my PR

[ctq123]

bundle should still be okay to use.

yes，it don't affect packaging, but it's not friendly to runtime

[dominikg]

this issue prevents sveltekit from updating to node-fetch 3.0.0

I've tried looking into it yesterday and wonder about a couple of things:

1. you are not tagging node internal modules with node: which is recommended for esm.
   Would tagging the internal modules make life easier for bundlers to detect new/unknown node internals?

2. the package.json files of node-fetch and fetch-blob do not contain "exports" mapping or "module" fields
   they may not be strictly required, but exporting package.json is a common courtesy and using exports is recommended here too The ESM move sindresorhus/meta#15

3. fetch-blob uses require in streams.cjs. (to avoid using top level await for node12 support i guess)
   Are there ways to avoid this direct require?

• https://nodejs.org/api/module.html#module_module_createrequire_filename
• use process.version to figure out if node:streams/web is available and lazily dynamic import the best available option on first
  use?
• ???

[jimmywarting]

1. this old issue made me belive i targeted 12.17 Support Node.js v12 #98 but the node.engine is set to 12.20. so we should be okey to use node:
2. so far i have not had any problems with it with the way it's right now.
3. yes it's to avoid top-level await for 12.20 support... haven't come up with any better solution yet

and lazily dynamic import

dynamic import is challenging const stream = new Blob().stream() is all sync would be different if stream returned a promise...

i have tried to best come up with a solution that don't import/depend on core node stuff. so that require can gracefully fail in Deno and Browser
like this result: https://cdn.jsdelivr.net/npm/fetch-blob/+esm
but others produce stuff like: https://jspm.dev/fetch-blob that fails totally