# debugger: Fix the JavaScript debug terminal scenario \(\#33924\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/01295aa687d726343e3b58ac4f0b3ae3b0d123eb)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 01295aa687d726343e3b58ac4f0b3ae3b0d123eb

Requested commit: 01295aa687d726343e3b58ac4f0b3ae3b0d123eb

Commit: 01295aa687d726343e3b58ac4f0b3ae3b0d123eb

Tree: 7bf929ba76e30120365b1636158724388679457e

Author: Remco Smits

Committer: GitHub

## Message

```
debugger: Fix the JavaScript debug terminal scenario (#33924)

There were a couple of things preventing this from working:

- our hack to stop the node REPL from appearing broke in recent versions
of the JS DAP that started passing `--experimental-network-inspection`
by default
- we had lost the ability to create a debug terminal without specifying
a program

This PR fixes those issues. We also fixed environment variables from the
**runInTerminal** request not getting passed to the spawned program.

Release Notes:

- Debugger: Fix RunInTerminal not working for JavaScript debugger.

---------

Co-authored-by: Cole Miller <cole@zed.dev>
```

## Parents

- [66e45818af4c93c64bf0707de1103cb23ecb34e6](https://git.cafe/gitcafe/zed/commit/66e45818af4c93c64bf0707de1103cb23ecb34e6?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/01295aa687d726343e3b58ac4f0b3ae3b0d123eb?format=markdown)