Describe the bug
when running react-scripts, passing "--watchAll=false" worked, while "--watch-all=false" doesn't. Given jest support both types of arguments, react-script should recognize them as well.
The code here seems to be the culprit: https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/scripts/test.js#L52
Did you try recovering your dependencies?
N/A
Which terms did you search for in User Guide?
N/A
Environment
N/A
Steps to reproduce
Any CRA project will do, just run npm run test -- --watch-all=false, react-scripts will still run watch mode.
Expected behavior
react-scripts should not run watch mode.
Actual behavior
react-scripts start jest in watch mode.
Reproducible demo
any CRA sample.
Describe the bug
when running react-scripts, passing "--watchAll=false" worked, while "--watch-all=false" doesn't. Given jest support both types of arguments, react-script should recognize them as well.
The code here seems to be the culprit: https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/scripts/test.js#L52
Did you try recovering your dependencies?
N/A
Which terms did you search for in User Guide?
N/A
Environment
N/A
Steps to reproduce
Any CRA project will do, just run
npm run test -- --watch-all=false, react-scripts will still run watch mode.Expected behavior
react-scripts should not run watch mode.
Actual behavior
react-scripts start jest in watch mode.
Reproducible demo
any CRA sample.