-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Swap isparta for babel-plugin-istanbul #330
Comments
FWIW I successfully made the switch to |
here's a specific example. Pretty easy switch. RoundingWellOS/marionette.toolkit@55993bd |
Nice! |
Note that this swaps isparta for https://github.com/jmcriffey/babel-istanbul, another library that is a "temporary fix." Eventually we will want to use just vanilla istanbul. It might be worth using istanbul alpha for reasons like jeffrifwald/babel-istanbul#56 (comment) |
My approach here will be to test babel-istanbul against istanbul beta on some project of mine. If istanbul beta is up to snuff, I'll use that. Otherwise, I'll switch to babel-istanbul. |
Ah jeez, yet another option: https://github.com/dtinth/babel-plugin-__coverage__ Coverage + transpiled code is in a rough place right now. That last one looks like it might be promising, but I'll have to investigate further... |
Looks like the |
There's also https://github.com/istanbuljs/babel-plugin-istanbul now (based off of ^) |
Ha I was literally just posting that @hzoo! Thanks for the link ;) In this comment it's mentioned that |
Ah I might have some answers for that - https://github.com/babel/babel/releases/tag/v6.11.3 Ref istanbuljs/babel-plugin-istanbul#5 - logan made some generator improvements but yeah I would check to confirm |
Alright – after some investigating I'm confident that switching to babel-plugin-istanbul is a good move forward. |
@bcoe We have it for babylon at least now https://github.com/babel/babylon/blob/master/.babelrc#L6 |
isparta isn't maintained, and it seems that the latest istanbuls might have better support for ES2015+.
The text was updated successfully, but these errors were encountered: