-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Safari TP browser target breaks core-js-compat targets-parser #755
Comments
It's a bug with |
Ah I see, I did think it was strange for TP (tech preview?) to show up in that query. No need for a fix on my end then, though you can still trigger the error using something like "unreleased versions" or "unreleased safari versions" so I think it's a valid bug. |
Merged
This was referenced Apr 12, 2020
This was referenced Apr 25, 2020
This was referenced May 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using require('core-js-builder') with the targets option set to a list of browsers. As of today "last 2 safari versions" expands to "safari 13" and "safari TP", which breaks core-js-compat with the following stack:
I guess the non-numeric version number throws it off. I can work around the issue for now by changing "last 2 safari versions" to "safari 13".
The text was updated successfully, but these errors were encountered: