Add Rust-based Istanbul code instrumentation #30529
Replies: 5 comments 3 replies
-
Please use #30174 for sharing what Babel transforms are being used, that way it's all kept in a single place. |
Beta Was this translation helpful? Give feedback.
-
One more reason to have this feature is when your code uses exclusive SWC features like |
Beta Was this translation helpful? Give feedback.
-
May this feature is related to this babel plugin with swc |
Beta Was this translation helpful? Give feedback.
-
Having the same problem. It would seem coverage would be one of the most basic features absolutely essential to have in place, but no... |
Beta Was this translation helpful? Give feedback.
-
Do you have any news about this feature? I tried this plugin, but it is broken :-/ . We use SWC and babel is not an option ! |
Beta Was this translation helpful? Give feedback.
-
Describe the feature you'd like to request
I currently use
babel-plugin-istanbul
to instrument my code to track code coverage while testing with Cypress:Describe the solution you'd like
I'd really like to use the new Rust-based compiler included by default in Next.js 12, but I can't until I'm able to instrument my code with Istanbul to track code coverage while testing.
Describe alternatives you've considered
Another possible solution would Next.js providing an option to use the custom
babel.config.js
only whileNODE_ENV=test
or something similar (i.e. I can still take advantage of the faster build times with SWC while deploying to production on Vercel but still use Istanbul to track code coverage while testing on GitHub Actions).Beta Was this translation helpful? Give feedback.
All reactions