Open tonivj5 opened 1 year ago
nx 15.6.3 debug don't works too I have tested couple nx versions and last version with working debug is 15.6.2
+100, makes work significantly more annoying 😂
PS. Adding debugger
at the beginning of your code makes functionality working again (bounds VS breakpoints which are after) but it's only a hotfix.
@Dzixxx what executor do you use?
If you create new project with nx 15.7.2 and add nest app, default executor will be @nrwl/js:node
and you solution don't works.
"serve": {
"executor": "@nrwl/js:node",
"options": {
"buildTarget": "api:build"
},
"configurations": {
"production": {
"buildTarget": "api:build:production"
}
}
},
I'm using @nrwl/node:node
but I also figured out that it works only if U will use at the beginning keyword debugger
. After removing it it will work as long as U have it connected 😢
+1 really a pain !
Experience of work with Node is terrible right now ;/
As a temporary workaround please try this: https://github.com/nrwl/nx/issues/14708#issuecomment-1457996600
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? I've tested even the latest v15.9.2 of nx and @nrwl/nest but still doesn't work. This is very needed! Any timeframe for this to be fixed?
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
As a temporary workaround please try this: #14708 (comment)
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. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
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.
have the issue with version 19.0.6
throw new Error(Could not find ${fileToRun}. Make sure your build succeeded.
);
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