[Feature request] Add inspectUri argument to Node debugger

Hey guys, React Native Tools team here. During migration of the extension on js-debug we found out that Node debugging scenarios doesn’t support inspectUri argument for discovering debugging target websocket via debugging proxy as browser scenarios does. Is it possible to add such an argument for Node scenarios?

[RedMickey]

Thanks for clarification, it seems that implementation of inspectUri parameter won’t make much sense for the extension in this case. So we are going to implement inspector socket lookup on RN extension side ourselves.

[connor4312]

In the Node attach case, you’re attaching to a process that is already started.

we’ll need to do inspector websocket lookup for debugging target from the proxy side

I think this is the correct thing for you to do. The inspectUri is useful in the Chrome launch case because there’s a lot of browser launching behavior that js-debug implements that would be impractical to reimplement in a the proxy. But if you already have a process running, it should be fairly trivial to do the websocket lookup there.