Bring back "NODE_OPTIONS": "--require /path/to/httptoolkit-auto-agent.js"

[samgermain]

I'm trying to set up the VSCode debugger to be monitored by HTTPToolkit and it's a lot more difficult to set up using proxies than it is to just put

  "env": {
    "NODE_OPTIONS": "--require /path/to/httptoolkit-auto-agent.js"
  }

into your launch.json

[pimterry]

Interesting! This obviously isn't officially supported, but if it works that's great, and I'm not aware of anything recently that would've broken this. If you need an officially correct NODE_OPTIONS value, the easiest way is to launch an intercepted terminal and read the env var there.

That said, watch this space - I have a very rough PoC for fully automatic VS Code interception, which I'm hoping to make some progress on in the next few weeks. Want to help me test that once it's ready?

[samgermain]

Interesting! This obviously isn't officially supported, but if it works that's great, and I'm not aware of anything recently that would've broken this. If you need an officially correct NODE_OPTIONS value, the easiest way is to launch an intercepted terminal and read the env var there.

That said, watch this space - I have a very rough PoC for fully automatic VS Code interception, which I'm hoping to make some progress on in the next few weeks. Want to help me test that once it's ready?

It doesn't work, chatgpt was telling me to do this, and I was thinking that this is how it worked in an earlier version, but it sounds like you're saying this was never the case

[samgermain]

That said, watch this space - I have a very rough PoC for fully automatic VS Code interception, which I'm hoping to make some progress on in the next few weeks. Want to help me test that once it's ready?

yeah i could probably help test it

[pimterry]

It doesn't work, chatgpt was telling me to do this, and I was thinking that this is how it worked in an earlier version, but it sounds like you're saying this was never the case

Hahaha, fantastic. I would really recommend assuming ChatGPT is wrong as a first step, rather than opening bug reports like this in future 😆

In reality, something along these lines might indeed be possible in theory, if you reference the right paths & scripts, but the exact command in the issue title here has never worked, and there's probably better options for most use cases anyway. No http-auto-agent.js file has ever existed.

yeah i could probably help test it

Ok, great, thanks. I'll send you a message at the usask.ca email from your profile once this is ready.

[samgermain]

Interesting! This obviously isn't officially supported, but if it works that's great, and I'm not aware of anything recently that would've broken this. If you need an officially correct NODE_OPTIONS value, the easiest way is to launch an intercepted terminal and read the env var there.

That said, watch this space - I have a very rough PoC for fully automatic VS Code interception, which I'm hoping to make some progress on in the next few weeks. Want to help me test that once it's ready?

something I've noticed from HTTP Toolkit intercepting all the requests on my computer is that the requests from VSCode extensions are annoying and clutter