-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto Attach is possible? #978
Comments
It looks like vscode-js-debug has client-side code that takes care of handling the If I read that right, it won't work out of the box with nvim-dap, and is also out of scope. I suspect it could be implemented in a way in the debug-adapter that works with a regular DAP client, without the need for custom extensions, but that would need to change in vscode-js-debug. Maybe worth creating an issue in their repository. That said, the customization & extension points of nvim-dap should be powerful enough to also implement it on the client side. E.g. you could try using the This might be something to implement in https://github.com/mxsdev/nvim-dap-vscode-js |
Thanks for the response @mfussenegger! I'll port the issue to the nvim-vscode-js repo |
Problem Statement
Hi, I've been configuring my nvim to debug on my editor a next.js app. And it works by starting a dev server with node options for debugging like this:
But I was wondering if it's possible to launch a next server from nvim like VSCode does.
This is my
launch.json
in VSCodeThis starts the server inside VSCode and the debugger is up and running
![image](https://private-user-images.githubusercontent.com/49499/248906854-fd92081d-61c4-4cf1-bd12-15e064c732da.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk0MDM3NzUsIm5iZiI6MTcxOTQwMzQ3NSwicGF0aCI6Ii80OTQ5OS8yNDg5MDY4NTQtZmQ5MjA4MWQtNjFjNC00Y2YxLWJkMTItMTVlMDY0YzczMmRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI2VDEyMDQzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMyMTEyNjU3YTViZDc4NDNlYWVjZTk1Y2VjMDU3ZmI0NmRjNzhmNjJjNjExMDc4YWRiZTQzNDQyMGI3ZDVjYjImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.tC2du9SUImWDP6gQEKcrzyqHwMQJBwRnyUQd5cp_CZM)
So you this would be possible use nvim-dap?
Thanks for this awesome project!
Possible Solutions
No idea.
Considered Alternatives
The alternative is to use
NODE_OPTIONS
in a terminal and then attach to that next server. Is fine but it would be awesome to be able to launch the server and attach within nvim.The text was updated successfully, but these errors were encountered: