Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot find module 'node:http` on AWS Lambda v14
See original GitHub issueUpgrade from version 3.0 to 3.1 produces a Runtime.ImportModuleError: Error: Cannot find module 'node:http on AWS Lambda runtime.
Screenshots
Your Environment
| software | version |
|---|---|
| node-fetch | 3.1 |
| node | 14 |
Additional context
Looks like node: prefix for imports added as part of https://github.com/node-fetch/node-fetch/pull/1346 causes this issue. I am happy to submit MR with a revert of this one, but I need to understand the reason why this prefix has been added here on the first place. Can you suport me on this one please @dnalborczyk ?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:16
- Comments:34 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
100s of 1000s of programmers will have to Google this error, come here, and apply the patch. That seems to be a colossal waste of time.
And esbuild is often used implicitly. I.e. if you use CDK with the NodeJsFunction, it calls esbuild. People might not even know that happens.
the latest
node.jsversion onawsis now14.18.1and therefore supports thenode:prefix forcommonjs.