-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Breaking Change]: Replace babel-istanbul-plugin and replace it by a webpack loader #27
Conversation
86a1d28
to
e56d027
Compare
e56d027
to
4f01c01
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
@kasperpeulen @yannbf I tried this with an app created using |
95139ce
to
c0c182a
Compare
c0c182a
to
92033f3
Compare
how should I expect to run the coverage on the webpack5 example folder ? I am getting following errors:
while
|
Closes #29
Closes #17
Closes #21
Closes #25
What Changed
The
babel-istanbul-plugin
was replaced by a custom webpack loader to enable support for all Webpack5 projects, independently, whether they are using Babel as a compiler or another solution, like SWCRelease Notes
babel-istanbul-plugin
with a custom Webpack loader to support coverage independently of the compiler used for Webpack5 projects. Before, the coverage addon only worked if Babel was used with Webpack5. Now, users might use other compilers like, for example, SWC.📦 Published PR as canary version:
1.0.0-canary.27.12a4851.0
✨ Test out this PR locally via: