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
What's happening
Existing Jest tests are failing with below error after upgrade to craco v7. Error disappears when -- coverage --coverageDirectory=coverage/jest option is removed from test script which leads to no coverage report.
Error:
● Test suite failed to run
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
By default "node_modules" folder is ignored by transformers.
Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation
Details:
/app/src/pages/Auth/MyComponent.tsx:577
_store$auth => {
^^^^^^^^^^^
SyntaxError: Unexpected identifier
> 1 | import MyComponent from './MyComponent';
| ^
2 | import Login from './Login';
3 | import Logout from './Logout';
4 |
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
at Object.<anonymous> (src/pages/Auth/index.ts:1:1)
What should happen
Test should pass as before upgrade
What's happening
Existing Jest tests are failing with below error after upgrade to craco v7. Error disappears when
-- coverage --coverageDirectory=coverage/jest
option is removed from test script which leads to no coverage report.Error:
What should happen
Test should pass as before upgrade
To reproduce
Run the
test:frontend
scriptCRACO version
(ex. 7.1.0)
CRACO config
package.json
myEnvironment.js
Additional information
Tried creating
jest.config.js
, does not help.The text was updated successfully, but these errors were encountered: