Created
July 28, 2019 20:23
-
-
Save purefan/6dfdb478c51908ef6aefc1a1dd5349be to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FAIL src/EngineChain/test.spec.js | |
● 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: | |
/path-to/node-uci/src/EngineChain/test.spec.js:1 | |
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { Engine, EngineChain } from '../'; | |
^^^^^^ | |
SyntaxError: Unexpected token import | |
at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17) | |
Test Suites: 17 failed, 17 total | |
Tests: 0 total | |
Snapshots: 0 total | |
Time: 5.659s | |
Ran all test suites. | |
npm ERR! Test failed. See above for more details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment