-
Notifications
You must be signed in to change notification settings - Fork 32
Debugging not working with new angular projects and --bundle #232
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
Comments
Same issue with me. |
Yes same here, the debug and hmr functinoality were fixed, in chrome debug it works fine, but the breakpoints are not working when --bundle or --hmr option are passed, and it is not ideal to switch between editor and chrome for debug. |
We've investigated this issue and it seems to happen only for Angular projects. The problem is caused by the "nativescript-dev-webpack/lazy-ngmodule-hot-loader", so in case you are not using HMR, you can safely comment the line where |
While a PR on this has been merged and is probably being tested, I wanted to point out that I get the same problem for a nativescript-vue app i.e. Environment
|
Hi @theunsa, |
Environment
CLI: @rc(5.1.1)
Cross-platform modules: 5.1.1
Android Runtime: 5.1.0
iOS Runtime: 5.1.0
VSCodeExtension: v.2018.12.11.1
To Reproduce:
tns create newApp --ng
cd newApp
code .
Add "tnsArgs": ["--bundle"] in the Launch on Android task.
Run the Launch on Android task.
Set a breakpoint.
The breakpoint is grayed out and marked as unverified
It is the same for ios.
(It is working with old templates for example @5.1.0).
Expected behavior
You should be able to debug the NativeScript apps in VSCode when the --bundle flag is passed.
The text was updated successfully, but these errors were encountered: