DAP (Debug Adapter Protocol) #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andresgutgon
force-pushed
the
feature/manson-nvim-dap
branch
from
5b32678
to
015e7f4
Compare
andresgutgon
force-pushed
the
feature/manson-nvim-dap
branch
5 times, most recently
from
d4dc123
to
4a13dd1
Compare
I want to be able to debug Node apps (Specially NextJS) app on backend side. nvim-dap use DAP protocol from Microsoft which is the one used by VSCode on their debugging experience. This is the same in Nvim. To be honest this has been fucking painful for several reasons. 1. First Next.js latest version has fucked their debugging experience. So I had to simplify the problem and first understand how node `--inspect` flag works on a simple Node server. Then I look into existing issues on Next.js and I discoverd that their debugging experience is broken in latest version. A [fix is comming in this PR](vercel/next.js#51467) 2. Second. After setting the `nvim-dap` plugin with the VSCode / JS debugging experience I spent a shameful amount of time hitting `node-terminal` debug mode when in reality was `pwa-node`. Yes, `pwa` is ultra weird and that took me time to figure out. [Issue here about it](microsoft/vscode#151910) FUCK! This was hard 馃槀
andresgutgon
force-pushed
the
feature/manson-nvim-dap
branch
from
4a13dd1
to
96eaf94
Compare
andresgutgon
commented
Jul 2, 2023
| name = "Attach to process", | ||
| type = "pwa-node", | ||
| request = "attach", | ||
| processId = dap_utils.pick_process, |
There was a problem hiding this comment.
The only way I managed to make this debugger in NextJS was by picking the process. At the moment I don't need to specify a .vscode/launch.json in my project. I just lunch the DAP UI and pick the process for the next app running in debug mode.
My package.json
"dev": "pnpm dev",
"dev:debug": "NODE_OPTIONS='--inspect' pnpm dev",
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WAT?
I want to be able to debug Node apps (Specially NextJS) app on backend side.
nvim-dapuse DAP protocol from Microsoft which is the one used by VSCode on their debugging experience. This is the same in Nvim.To be honest this has been fucking painful for several reasons:
--inspectflag works on a simple Node server. Then I look into existing issues on Next.js and I discoverd that their debugging experience is broken in latest version. A fix is comming in this PRnvim-dapplugin with the VSCode / JS debugging experience I spent a shameful amount of time hittingnode-terminaldebug mode when in reality waspwa-node. Yes,pwais ultra weird and that took me time to figure out. Issue here about itTODO
Take a look to mason installation for dap adapters.Doesn't work. Maybe in the futureFUCK! This was hard 馃槀