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
Running --runInBand or --maxWorkers=1 and --no-cache invokes TypeError: Cannot read property 'some' of undefined in @babel/helper-module-transforms/lib/index.js
#7762
Closed
ethernal opened this issue
Jan 30, 2019
· 3 comments
Title is long but should make finding issue for others easier.
🐛 Bug Report
Running Jest --runInBand or --maxWorkers=1and--no-cache invokes TypeError: Cannot read property 'some' of undefined in @babel/helper-module-transforms/lib/index.js
Removing either of them solves the issue.
Running yarn or npx jest --no-cache --maxWorkers=2 NO issue.
Running yarn or npx jest --runInBand NO issue .
Running yarn or npx jest --no-cache NO issue .
Running yarn or npx jest --runInBand --no-cache invokes the ERROR.
Important notice: I work on Windows 10 (1803) and I have seen a lot of issues with file races etc. Not sure if this is related to #4444 or other tickets.
This is fixed by upgrading to Jest 24. You'll get an error about moduleFileExtensions, but that's fixed in master by #7751. Hopefully will get a release today 🙂
$ npx jest --runInBand --no-cache --config test/jest.test.js● Deprecation Warning: Option "setupTestFrameworkScriptFile" was replaced by configuration "setupFilesAfterEnv", which supports multiple paths. Please update your configuration. Configuration Documentation: https://jestjs.io/docs/configuration.html PASS test src/__tests__/example.test.ts ✓ AddFunction (4ms) AddFunction ✓ adding positive integers ✓ adding negative integers (1ms) ✓ adding positive and negative integers ✓ adding positive floats ✓ adding negative floats (1ms) ✓ adding positive and negative floats PASS test src/__tests__/app.test.tsx ✓ renders (23ms)----------|----------|----------|----------|----------|-------------------|File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s |----------|----------|----------|----------|----------|-------------------|All files | 0 | 0 | 0 | 0 | |----------|----------|----------|----------|----------|-------------------|Jest: Coverage data for ./src/index.tsx was not found.Test Suites: 2 passed, 2 totalTests: 8 passed, 8 totalSnapshots: 0 totalTime: 4.556sRan all test suites.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Title is long but should make finding issue for others easier.
🐛 Bug Report
Running Jest
--runInBand
or--maxWorkers=1
and--no-cache
invokesTypeError: Cannot read property 'some' of undefined in @babel/helper-module-transforms/lib/index.js
Removing either of them solves the issue.
Running yarn or npx jest --no-cache --maxWorkers=2 NO issue.
Running yarn or npx jest --runInBand NO issue .
Running yarn or npx jest --no-cache NO issue .
Running
yarn
ornpx jest --runInBand --no-cache
invokes the ERROR.Important notice: I work on Windows 10 (1803) and I have seen a lot of issues with file races etc. Not sure if this is related to #4444 or other tickets.
To Reproduce
Clone the latest commit from
https://github.com/ethernal/react-boilerplate
Steps to reproduce the behavior:
in terminal run:
yarn install
and thenyarn / npx jest --no-cache --runInBand
or
yarn
/npx jest --no-cache --maxWorkers=1
Expected behavior
All existing tests should pass with
yarn jest --no-cache --runInBand
.Link to repl or repo (highly encouraged)
https://github.com/ethernal/react-boilerplate
Issues without a reproduction link are likely to stall.
Run
npx envinfo --preset jest
Paste the results here:
The text was updated successfully, but these errors were encountered: