You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Crashes when starting an application using ES6 modules #165
Debugger listening on ws://127.0.0.1:4363/ffc5c2f7-0765-4396-b0d5-6548fc3e238a
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
(node:65673) ExperimentalWarning: The ESM module loader is experimental.
Error: linking error, dependency promises must be resolved on instantiate
at checkComplete (internal/loader/ModuleJob.js:75:27)
at moduleJob.linked.then (internal/loader/ModuleJob.js:58:11)
at <anonymous>
Waiting for the debugger to disconnect...
So my goal is to basically somehow defer the debug attach step for at least a moment so things can fire up properly.
I've added "noDebug":true to my launch configuration and am using Chrome to debug instead, for now. Is that really all I can do? Would passing some sort of extra "delay" parameter to launch config be a big deal to implement?
The associated issues on node are closed and I'm unable to repro in 10.16. I tried a synchronous import x from './module' as well as the async import('./module') statement, and also tried inserting:
Activity
jpike88 commentedon Nov 23, 2017
When using integrated terminal, I get this error:
jpike88 commentedon Nov 23, 2017
Just tried with Chrome debugger directly, same error... looks like VSCode may not be the issue here
jpike88 commentedon Nov 23, 2017
Closing as this is not VSCode's problem
jpike88 commentedon Nov 24, 2017
I've opened an issue here:
nodejs/node#17280
jpike88 commentedon Nov 24, 2017
Actually, this is still relevant, I'll reopen unless someone decides otherwise
jpike88 commentedon Nov 24, 2017
The problem is that the debugger attaches too early. There needs to be a way to delay the attach step.
roblourens commentedon Nov 24, 2017
Delay until when?
jpike88 commentedon Nov 24, 2017
Perhaps by 2 or 3 seconds, as it's currently interfering with ES6 module linking.
See:
nodejs/node#17280
roblourens commentedon Nov 24, 2017
It's node's bug, but you can use one of the workarounds from the other issue.
jpike88 commentedon Nov 24, 2017
So my goal is to basically somehow defer the debug attach step for at least a moment so things can fire up properly.
I've added "noDebug":true to my launch configuration and am using Chrome to debug instead, for now. Is that really all I can do? Would passing some sort of extra "delay" parameter to launch config be a big deal to implement?
roblourens commentedon Nov 24, 2017
I don't want to add it if it's just a workaround for a bug in Node.
connor4312 commentedon Oct 8, 2019
The associated issues on node are closed and I'm unable to repro in 10.16. I tried a synchronous
import x from './module'as well as the asyncimport('./module')statement, and also tried inserting:to make sure the debugger would attach before hitting these statements. Everything seemed to work well.
roblourens commentedon Oct 8, 2019
Thanks!