Skip to content
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

SourceMap on browser not working #223

Closed
craftzdog opened this issue Jan 29, 2016 · 3 comments
Closed

SourceMap on browser not working #223

craftzdog opened this issue Jan 29, 2016 · 3 comments

Comments

@craftzdog
Copy link

Logging via debug module on browser causes source map not working.
Setting Chrome's framework blackboxing also does not work (because of webpack URL?).
How to manage it?

screen shot 2016-01-29 at 20 43 55

@craftzdog craftzdog changed the title SourceMap on Browser SourceMap on browser now working Jan 29, 2016
@craftzdog craftzdog changed the title SourceMap on browser now working SourceMap on browser not working Jan 29, 2016
@jaredcat
Copy link
Contributor

👍

@iam4x
Copy link
Owner

iam4x commented Feb 1, 2016

I don't understand your issue, you have the file name with the line correctly set in your console I see?

@iam4x iam4x closed this as completed Apr 2, 2016
@craftzdog
Copy link
Author

Sorry for my poor expression.

When I use console.log the chrome dev tools add a link to the line of code where that console.log statement was executed.
But with debug module, the dev tool always links every logs to debug/browser.js:112.
This issue is discussed at debug-js/debug#229.
A simple solution is usually to use Blackboxing that lets blackbox a source file so the debugger will not jump into that file when stepping through code you're debugging.
The problem was the Blackboxing is somehow not working in this boilerplate in my case.

My workaround is to set devtool to eval-source-map in base.config.js and to use the latest Chromium instead of Google Chrome because the Blackboxing is possibly not working for inline scripts such as created with Browserify (See debug-js/debug#198 (comment)).
With this configuration dev tool links expected lines like following.

Before:
screen shot 2016-04-07 at 18 57 14

After:
screen shot 2016-04-07 at 18 47 38

it may not be this project's issue though I'd just report.
regards.

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

No branches or pull requests

3 participants