-
Notifications
You must be signed in to change notification settings - Fork 39
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
Can't set breakpoint in webworker #9
Comments
are you sure your transforms are not the problem? |
I have no idea, I'm kinda new to this. However, when an error occur in the webworkified worker, the stopping point in the Chrome debugger is in an embedded data URI. I.e. the source of the worker has been converted into a data URI. So, it's not actually executing the source that was transformed by browserify, which would have sourcemap annotations. |
Also, I can set breakpoints in other code which was processed by the same set of transforms. |
in the mean time you can use |
Could you elaborate a little on what you mean by |
I see, thanks. |
Also running into this issue. The debugger statement does work, but it would be nice to be able to set breakpoints as well. Anyone had any luck getting breakpoints to work? Edit: Just realized that once the debugger statement has been hit, you can set breakpoints within that file and they'll be hit as well. |
This is something that's not possible to fix because worker sources are created dynamically (with blob URLs), so breakpoints you set on a generated source don't persist after reloading a page.
|
See also http://stackoverflow.com/a/24198720/52207. Once the webworker is paused on start, you can set breakpoints within it. |
I'm using browserify and webworkify with sourcemaps but any breakpoint I set in the sourcemap'd file in Chrome is not hit.
My gulpfile task looks like this:
The text was updated successfully, but these errors were encountered: