Add option to show getter evaluation without expanding

When inspecting an object with getters, the old debugger would show the getters as regular properties, evaluating them and showing their return values inline with the rest of the other properties. In this screenshot, all the __debug properties are actually getters on the Node’s prototype:

In the new debugger, each getter has to be clicked to be evaluated:

Presumably the motivation here is that getters can cause side effects, and it would be horrible if observing a variable in the debugger caused observable effects to your program state. However, in TypeScript, all our getters are pure, and we rely on these __debug-prefixed ones heavily to be able to identify objects at a glance, and those extra clicks add up to a lot of pain.

I would suggest a configuration option that could be set to opt into the old inlining behavior.

[connor4312]

We fleshed this out some more today, details in https://github.com/microsoft/vscode-js-debug/issues/548. You will still need pwa-node through the upcoming June release. After that point, the previous debug adapters will be removed and you’ll no longer need to use pwa-node.

We will probably keep the pwa- prefixed-configs around for at least one release to allow for migrations.

[connor4312]

Ah. It looks like this doesn’t work if you use the redirection from the existing Chrome/Node configurations – you have to launch with the pwa-* debug type.

I’m not sure I want to fix that – it adds some extra duplication and dependency to the standalone debug server, and I think that if people are tinkering with their js-debug options they would be satisfied prefixing their launch config until such time as js-debug becomes default.