Nest.js: Unable to import
See original GitHub issueProblem
Compilation fails when using tle.js with nest.js:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: <redacted>/node_modules/tle.js/dist/tlejs.umd.js
require() of ES modules is not supported.
require() of <redacted>/node_modules/tle.js/dist/tlejs.umd.js from <redacted>/dist/services/spacecraft-data.service.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename tlejs.umd.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from <redacted>/node_modules/tle.js/package.json.
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1089:13)
at Module.load (internal/modules/cjs/loader.js:937:32)
at Function.Module._load (internal/modules/cjs/loader.js:778:12)
at Module.require (internal/modules/cjs/loader.js:961:19)
at require (internal/modules/cjs/helpers.js:92:18)
at Object.<anonymous> (<redacted>/src/services/spacecraft-data.service.ts:5:1)
at Module._compile (internal/modules/cjs/loader.js:1072:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
at Module.load (internal/modules/cjs/loader.js:937:32)
at Function.Module._load (internal/modules/cjs/loader.js:778:12)
Workaround
Remove the "type": "module",
line from the package.json
Solution
I don’t know (yet). Maybe remove the line and everything would be fine? Or does that cause other problems?
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Common errors - FAQ - A progressive Node.js framework
To fix that, make sure you're importing the class reference or use a custom token with @Inject() decorator. Read the custom providers page....
Read more >Unable to import ESM module in Nestjs - Stack Overflow
I am having a problem with importing ESM modules in my project based on Nest.js. As far as I understand, this problem is...
Read more >Nest can't resolve dependencies when import module from ...
Generally speaking you should never import a module when you are already inside the module itself. It's a guaranteed circular dependency. Import ...
Read more >NestJS: Resolving Dependency Injection - Tevpro
The DI framework was unable to resolve on the dependencies (AuthService) in the AuthContoller. // auth.contoller.ts import { Controller, UseGuards, Req, Body } ......
Read more >Inject Service From Another Module in NestJS (2022)
Great. Let's import the ItemModule inside our PlayerModule in order to get access to ItemService. Please change src/player/player.module.ts from ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, thanks for the info and the “temporary” solution. That’s way better than my workaround. I’ve implemented it and it works so far. Let’s hope they’ll implement it soon.
Okay, I tested it. It works so far. No errors and the functions I’m using are executing normally, as far as I see. Even with Nest.js. Thanks very much!