Debugging Local generators

[bosycom]

Documentation issue

• Reporting a typo
• Reporting a documentation bug
• Documentation improvement
• Documentation feedback

Is there a specific documentation page you are reporting?

Debugging Local generators

Additional context or description

1. Please add description on how to setup debugging of local generators for Jetbrains IDE such as WebStorm/PhpStorm etc. by providing a working example that actually hits the breakpoints in a generator.ts file.
2. Following the instruction on the doc page, I could not get debugging to work correctly. VSCode hits breakpoints in den webpack JS file instead of the generator.ts file. This might be a sourceMaps issue, but I don't think that it is specific to my workspace, so any help by improving the doc is appreciated.

[cameronevans]

been running into the same issue, was only able to get a source map was by uninstalling swc so it would fall back to ts-node

[isaacplmann]

The PR fixes item 2 in your list. I recommend opening a separate issue for item 1.

[jgarciaokode]

hi @Cammisuli @AgentEnder, can you expand on how are you supposed to debug a local nx generator? Following the instructions in the docs https://nx.dev/recipes/generators/local-generators#debugging-generators does not seem to work. I only managed to get it working by invoking node --inspect-brk node_modules/@nrwl/cli/bin/nx.js generate @mapfre-tech/mar-nx:front-properties --project ang-test-app and then invoking Debug:Attach to node process command in vscode. But it is a compiled version and i can see in the docs you are supposed to debug on the same .ts you are writing code

[jgarciaokode]

ok, I just realized there is a "fix" already merged in master. I checked and this commit is not in the latest version of @nrwl/nx-plugin so i guess we will have to wait for the next version

I guess with this, the problem is solved, will try it out and report back if it is not working

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.