Meaningful node inspect context titles

[filmerjarred]

Problem: When inspecting multiple node contexts using the new --inspect flag paired with the dedicated node inspect in chrome dev tools, knowing which process you're currently inspecting can be confusing as they're all called "Nodejs Main Context" as per (I think):

node/src/inspector_agent.cc

Line 302 in 5886e20

contextCreated(env->context(), "Node.js Main Context");

Potential solutions:

• Taking an optional environment variable like NODE_CONTEXT_TITLE (looks like the env might already be being passed in there, not sure if same env as process.env?)
• Could pass in a flag along the lines of --inspect-context-title

[Fishrock123]

Shouldn't it just take process.title?

[filmerjarred]

Often the process title is just 'npm' or 'node' so you get the same problem. Ideally, I'd like to click the context dropdown and see 'Service A' and 'Service B' for ease of debugging. Changing process.title also has limitations and side effects on other things as I understand it

[addaleax]

@bnoordhuis I guess this was fixed by #17087?

[filmerjarred]

Looks to be 👍