Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ➜ npx jest
- FAIL components/__tests__/Button.spec.tsx
- ● Test suite failed to run
- Jest encountered an unexpected token
- This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.
- By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".
- Here's what you can do:
- • 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/en/configuration.html
- Details:
- /Users/kjaer/our-cool-nextjs-app/components/__tests__/Button.spec.tsx:9
- var wrapper = enzyme_1.mount(<p>Jest Hello World</p>);
- ^
- SyntaxError: Unexpected token <
- at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
- at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
- Test Suites: 1 failed, 1 total
- Tests: 0 total
- Snapshots: 0 total
- Time: 1.522s
- Ran all test suites.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement