-
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
Trouble configuring project with angular + jest + typescript #672
Comments
Hi @Benlemen thanks for trying out stryker! The challenge with Jest is that it needs the node_modules folder directly located next to your sourcefiles. In a Stryker sandbox, this is not the case. The stryker sandbox can be found under We're thinking of a solution for this problem by symlinking the node_modules into the sandbox directories. @simondel did an test with this setup and it seems to work for jest. We're just not sure if it might have side effects for other setups so we might not enable it by default, but via a config setting. @simondel what do you think? |
How about |
@nicojs that config setting sounds good! It's long but if you read it, you may know what it does. Making it shorter will make it more complex. |
As discussed with @nicojs Let's not support this using the commandline for now, only using the config. |
Well... Let's leave the default to indeed symlink. I see this solution helping more people that way. We'll leave the option to not symlink node modules. |
Summary
Hi !
I'm having trouble configuring stryker on an angular + yarn + jest + typescript project.☺️
My test suite works well using
yarn jest
. Here is the commit if you want to reproduce : borsini/simple-home-accounting@c685cbeAny help would be fantastic
I first met this error :
My jest configuration uses an angular preset. I added the
preprocessor.js
file intostryker.conf.js
, but now I have the following error. It seems stryker tries to transpile it. It is clearly not the solution...Stryker config
Jest config (package.json)
Stryker environment
Your Environment
The text was updated successfully, but these errors were encountered: