-
Notifications
You must be signed in to change notification settings - Fork 250
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
Babel parse error on flow syntax #2704
Comments
I have just confirmed that my suspicion was correct – that this is due to the |
Thanks for bug report and triage! This should be a simple fix. Could you maybe create a small hello-world-like example that reproduces this issue? We would be happy to add it to our e2e test suite so it won't ever break again. |
I tried my hand at reproducing this myself, but couldn't. See zip. Unzip and cd into the directory. Then run npm i
npm run test # see that normal unit testing works
npm run test:mutation # see that Stryker works |
@nicojs here's a MRE: https://github.com/swist/stryker-flow-bug Just follow the steps you outlined in your comment :) |
Summary
I am getting a
BABEL_PARSE_ERROR
on flow type syntax, and I think it's because stryker is adding instrumentation to the top of my files, which means that the// @flow
pragma is no longer at the top of those files, so the babel flow plugin no longer runs against those files.Stryker config
Stryker environment
Your Environment
Add stryker.log
The text was updated successfully, but these errors were encountered: