-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
After update to latest (15.7.x
) debugger doesn't attach to breakpoints
#15159
Comments
nx 15.6.3 debug don't works too |
+100, makes work significantly more annoying 😂 PS. Adding |
@Dzixxx what executor do you use?
|
I'm using |
+1 really a pain ! |
Experience of work with Node is terrible right now ;/ |
As a temporary workaround please try this: #14708 (comment) |
Still a issue |
+1 want this back |
This is becoming more and more frustrating. This tool should help save time, yet every single upgrade one has to spend hours and hours trying to work around basic things that stopped working. Are there no tests for this? Please fix. |
any update on this? |
Also bumping up. This just stopped working for me one day, and it is very frustrating. |
Really frustrating! still breakpoints are not attaching on "nx": "16.1.0", |
Still not working, so frustrating |
You should definitly use this as a temporary workaround... |
Currently using 16.3.2 and I still can't fix the breakpoints. Other colleagues have already commented, but @gdraganic solution works perfectly. |
I am curious if anyone has upgraded to 16.9.1 to see if breakpoints work? The workaround works for me, but it does seem like it takes a bit longer to hot-reload after changes are made. Not sure if it's related to the work-around. |
Indeed, I upgraded to nx 16.9.1, but also my docker image to node:20.7-alpine3.18, and I can confirm that everything works great without having to apply @gdraganic's solution. In my case, I am not experiencing performance problems, indeed, possibly because I have upgraded my node version from 20.2 to 20.7, I have noticed that both the change detection and transpilation process is considerably faster. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Up! |
Confirming the issue still remains as of version 18.3.2 Running a node CLI-based tool |
Is there any progress on this issue? |
bump. |
throw new Error( |
Update - I updated my project to v19.6.1 and was able to successfully debug via vs code 🎉🎉🎉 My launch.json config looks like this:
|
I have 2 apps (node.js and nest.js) and run them by running |
see my comment here: #14708 (comment) |
This issue has been automatically marked as stale because it hasn't had any activity for 6 months. |
|
Current Behavior
I use
Javascipt debug terminal
functionality from vscode, it's similar to its auto-attach but on demands. After update to latest nx version, I can not debug my app in this way.Expected Behavior
The debugger is attached to the process
GitHub Repo
https://github.com/tonivj5/nx-debug-bug
Steps to Reproduce
git clone https://github.com/tonivj5/nx-debug-bug.git
npm i
apps/test/src/main.ts
Ctrl + p
(or your shortcurts) and write>javascript debug terminal
, enter./node_modules/.bin/nx serve test
git checkout no-debug
npm i
./node_modules/.bin/nx serve test
Nx Report
Failure Logs
Additional Information
No response
The text was updated successfully, but these errors were encountered: