v1.x.x backport request: Add a fallback for Chrome dev tools strange behavior #210
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pr aims to backport an already implemented fix (see #186) to the 1.x.x version track, for a breaking change introduced by the current stable version of Chrome.
There doesn't seem to be a 1.x.x version track for core-js, but I thought I'd try to this request anyway. 😉
This could be seen as a critical bugfix, since babel 5.x.x still uses the core-js in the
^1.0.0
range. I can imagine quite a few devs who are maintaining an app with babel 5.x.x would appreciate this backport.Also, thanks for the original fix! You've made it easy to apply a temporary hotfix to my own app.
Note: I don't intend this pr to actually be merged into
master
. Perhaps you could create a1.x.x
branch, if you go ahead with this pr?