How do I enable console output?

[vinicius507]

When trying to execute package.json scripts on nvim-dap with the following configuration:

{
    type = "pwa-node",
    request = "launch",
    name = string.format("Run script: %s", name),
    cwd = "${workspaceFolder}",
    env = {
      NODE_OPTIONS = "--inspect",
    },
    runtimeExecutable = pm,
    runtimeArgs = { "run", name },
    resolveSourceMapLocations = { "${workspaceFolder}/**", "!**/node_modules/**" },
    sourceMaps = true,
    skipFiles = { "<node_internals>/**", "node_modules/**" },
}

I get no console output. Is there any way for me to modify this so it works?

[igorlfs]

Olá,

Is there any way for me to modify this so it works?

That's a great question, actually. The short answer is that you can't get the output in the console, but rather in the REPL.

That happens because the js-debug-adapter is full of quirks to handle multiple sessions. There's a root session, which then creates another session, to spawn the command that is specified in the configuration (e.g., for the configuration you provided, the package.json script is run). If the command then spawns another process, a new session is also created and so on.

But notably, these child sessions do not have an assigned terminal (the js-debug-adapter does not request one), which means that the "console view" (or anything, really) can't display the output for that specific process. The way the js-debug-adapter deals with that is by sending the output of every session to the REPL.

Additionally, the naming can be a bit confusing. Within nvim-dap, the REPL is what's usually referred to as the "Console" (i.e., browser console). And nvim-dap-view's "console view" is meant to show the terminal associated with the current session.

[vinicius507]

Nossa, passei o olho rápido nem vi que era BR 🤣

Thanks a lot for the thoughtful response. Now I understand the issue. Great work, by the way. It's a great plugin.

[vinicius507]

@igorlfs I'm trying to use console = "integratedTerminal" with windows.terminal.start_hidden = true and the console always opens (oddly enough, nvim-dap-view does not open even with auto_toggle = true) without the filetype set to dap-view-term.

2025-10-22.16-07-34.mp4

[igorlfs]

Hey,

Please, do not report issues on closed discussions.

I'm trying to use console = "integratedTerminal" with windows.terminal.start_hidden = true and the console always opens (oddly enough, nvim-dap-view does not open even with auto_toggle = true) without the filetype set to dap-view-term

This sounds like a lazy-loading issue. Ensure that nvim-dap-view is loaded before you try to start a session. If you're using lazy.nvim, my recommendation is to add nvim-dap-view as a dependency for nvim-dap (not the other way around!).

But your description does highlight an odd interaction between the options: auto_toggle overrides start_hidden, and that's undocumented. To be fair, in hindsight, start_hidden was a mistake (treating the terminal specially is a bit silly). EDIT: tracked in #123