Promise variables show as undefined although they are not

[jrieken]

See attached screen shot. The promise argument shows as undefined everywhere but the console reveals the truth when you 'use' it.

[jrieken]

to reproduce:

• set a breakpoint in the unhandledRejection handler
• execute the snippet(*) below in an extension (as command for instance)

when it breaks promise is shown as undefined

*snippet

      const rejectedPromise = new Promise((resolve, reject) => {
            reject('foo');
        });

        setTimeout(() => {
            rejectedPromise.catch(() => {
                console.log('handing error now');
            });
        }, 2000);

[weinand]

@jrieken this is a limitation of the node v8 debugging protocol. node-inspector shows the same behavior:

[rebornix]

Ran into the same situation. Whenever I create a new promise, the intellisense keeps saying it's undefined.