Bluebird: Exception while debugging on VS Code

[gauravsharmadev]

The bluebird is throwing exception while debugging on VSCode.

Exception has occurred: Error
Error
at Object. (/node_modules/bluebird/js/release/util.js:378:12)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at module.exports (/node_modules/bluebird/js/release/promise.js:14:12)
at Object. (*/node_modules/bluebird/js/release/bluebird.js:9:36)

[benjamingr]

Turn on long stack traces and show the error you get with them.

Promise.config({longStackTraces: true})

[gauravsharmadev]

I am not using bluebird... it's being used by some third party

[benjamingr]

You can set the appropriate environment variable instead then: http://bluebirdjs.com/docs/api/environment-variables.html

[miteshrathod09]

@sharma02gaurav @benjamingr Any resolution?

[gauravsharmadev]

@jainmitesh09 I don't know. It was a weird issue. Seems like package was broken or something. I re-clone my repository and installed dependency and after that It started working. Not a proper solution though but i don't know why?

[miteshrathod09]

@petkaantonov can you please update?

Error logs:

Exception has occurred: Error
Error
    at Object.<anonymous> (/work/tionodeweb/node_modules/bluebird/js/main/async.js:3:12)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at module.exports (/work/tionodeweb/node_modules/bluebird/js/main/promise.js:30:13)
    at Object.<anonymous> (/work/tionodeweb/node_modules/bluebird/js/main/bluebird.js:9:39)

[miteshrathod09]

@sharma02gaurav turning off the breakpoints for all exceptions helps for now.

[jollifft]

Turning off all breakpoints also resolved the issue for me.

[edward12699]

if turnning off all breakpoints,,then debug is meanless,,,

[jollifft]

Sorry @edward12699 I didn't explain that very well. The issue was caused by me clicking "Debug -> Enable All Breakpoints". To resolve the issue, I clicked "Debug -> Disable All Breakpoints" and then manually enabled the breakpoints I needed one at a time. Hope this helps!

[miteshrathod09]

It took a while for me to get that too. Thanks @jollifft !

[maxgardner]

Ran into this as well and was able to use the skipFiles option in the debug config to ignore all packages:

https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_skipping-uninteresting-code-node-chrome

I like this because it still allows me to debug with all exceptions. Hope this helps anyone else who has found their way here.