-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Enable eval-source-map for firefox #5060
Conversation
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Stale be gone! |
@Timer should we rebase and try to land? It seems like chrome is unblocked... |
Yeah, I think it's about time to switch to this by default. |
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Switches to eval-source-map, which is easier for webpack to recompute when a file changes and has column based mappings, which lets firefox devtools show original variable in the debugger and evaluate original expressions in the console.
hmm, seeing some build errors
|
I tagged this for next release so it stops falling through the cracks :-) |
@jasonLaster that error is also on master. Not sure what's going on. |
@ianschmitz thanks for the bump. |
YOLO |
Thanks @jasonLaster for all the time you spent on this, including our pair-programming! It was a pleasure working with you. |
Switches to eval-source-map, which is easier for webpack to recompute when a file changes and has column based mappings, which lets firefox devtools show original variable in the debugger and evaluate original expressions in the console.
Follow up for #4930.
This enables
eval-source-map
for firefox browsers, which makes it possible to see mapped scopes and variables. Hopefully in a couple of months chrome will also supporteval-source-map
and we can drop the check.