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 }}
Repository navigation
UNABLE TO DEBUG - Linking error, dependency promises must be resolved on instantiate #17280
This error seems to be triggered whenever I try to attach a debugger to the application, using the --inspect-brk flag.
Interestingly, If I use the --inspect flag and attach the debugger shortly after giving my application a moment to figure itself out, everything is fine.
Also importantly, it appears that if I cut big chunks out of my application reducing initialisation time with lots of modules taking ~2 seconds to fire up down to an almost instant startup time... then running with --inspect-brk worked ok as well.
I can only conclude that premature attachment of the debugger is interfering with the ES6 module initialisation stage if that stage is sufficiently long enough... this is a critical issue for developing an codebases with a half decent size.
changed the title [-]Linking error, dependency promises must be resolved on instantiate[/-][+]UNABLE TO DEBUG - Linking error, dependency promises must be resolved on instantiate[/+]on Dec 12, 2017
Activity
[-]Linking error, dependency promises must be resolved on instantiate[/-][+]UNABLE TO DEBUG - Linking error, dependency promises must be resolved on instantiate[/+]jpike88 commentedon Dec 12, 2017
this seems rather important... is there an ETA on this?
devsnek commentedon Dec 12, 2017
it appears to be being handled with #17360 and #17340