You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
The module babel-core/register is required in order to transform the es2015 code. I use ignore-styles because I am using SASS in my React components (which also needs to be compiled or it throws errors).
These root-level hooks, using the --require option, are modules that are run first, before any tests are loaded (?).
I think that all that needs to be done is ensuring that these "root-level hooks" are the first files that are fed to Mocha when using it programmatically. I don't have much experience there, but that's what I've gathered from looking around a bit.
The text was updated successfully, but these errors were encountered:
Sorry for the late response. I have been thinking about this for a while. We would first need to add support for es2015 into Stryker. As of now, Stryker is not able to mutate all es2015 code (it breaks on import statements).
We'll first investigate that, before fixing this issue. Meanwhile, if anyone wants to have a go, please do so.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From this issue with the core project.
My environment is setup using Babel, as all my source and tests are written in es2015.
To be able to run my tests using mocha, I run the following command:
The module
babel-core/register
is required in order to transform the es2015 code. I useignore-styles
because I am using SASS in my React components (which also needs to be compiled or it throws errors).These root-level hooks, using the
--require
option, are modules that are run first, before any tests are loaded (?).I think that all that needs to be done is ensuring that these "root-level hooks" are the first files that are fed to Mocha when using it programmatically. I don't have much experience there, but that's what I've gathered from looking around a bit.
The text was updated successfully, but these errors were encountered: