Skip to content

Debugging not working with --bundle #222

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

Closed
DimitarTachev opened this issue Nov 28, 2018 · 6 comments
Closed

Debugging not working with --bundle #222

DimitarTachev opened this issue Nov 28, 2018 · 6 comments

Comments

@DimitarTachev
Copy link
Contributor

Environment

  • CLI: 5.0.1
  • Cross-platform modules: 5.0.0
  • Android Runtime: 5.0.0
  • iOS Runtime: 5.0.0
  • VSCode: 1.29.1

To Reproduce

  1. tns create newApp --js
  2. cd newApp
  3. code .
  4. Add "tnsArgs": ["--bundle"] in the Launch on Android task.
  5. Run the Launch on Android task.
  6. Set a breakpoint.
  7. The breakpoint is grayed out and marked as unverified (most probably the bundle js map is not handled properly).

Expected behavior
You should be able to debug the NativeScript apps in VSCode when the --bundle or --hmr flags are passed.

@coding-style-review
Copy link

This issue was introduced by the commit from here: #213

That commit solves the debug extension issue for the angular template, but adds other issues for the rest of the templates.

@18clans
Copy link

18clans commented Jan 17, 2019

Was this ever fixed? I'm still having this same issue.

@DimitarTachev
Copy link
Contributor Author

@18clans, it was fixed in the new version of the launch.json. If you are using an old project, check your ./.vscode/launch.json file and delete the sourceMapPathOverridesproperty.

@xdubx
Copy link

xdubx commented Mar 20, 2019

Nop still not working. v.0.9.0 with nativscript +vue

@DimitarTachev
Copy link
Contributor Author

@xdubx Maybe there are some source maps issues in your app (e.g. the devtool property is not configured properly - here's the proper setup).

I suggest you update nativescript-dev-webpack to the latest version and execute its update scripts with ./node_modules/.bin/update-ns-webpack --configs in order to get the latest webpack.config.

If this doesn't help, please open a new issue following the issue template in order to allow us investigate it further.

@xdubx
Copy link

xdubx commented Mar 21, 2019

update the webpack config works for me thx for the fast reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants