Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected token import in all specs #597

Open
jamiewhittle opened this issue Nov 14, 2018 · 2 comments
Open

Unexpected token import in all specs #597

jamiewhittle opened this issue Nov 14, 2018 · 2 comments

Comments

@jamiewhittle
Copy link

Same as this issue: #402

`FAIL src/actions/fuelSavingsActions.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:

tools\enzymeTestAdapterSetup.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { configure } from 'enzyme';
                                                                                         ^^^^^^

SyntaxError: Unexpected token import

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)`

Node version:
v8.11.4

npm version:
5.6.0

Operating system:
Windows 10

Steps to reproduce:
$ git clone https://github.com/coryhouse/react-slingshot.git
$ npm run setup
$ npm start -s

It builds and runs OK, but all the tests fail.

@kwelch
Copy link
Collaborator

kwelch commented Nov 15, 2018

Do you have latest? I just pulled latest and ran test without an issue. On notable difference in my test is that it was on OSX.

@jamiewhittle
Copy link
Author

Hi, thanks for getting back to me. Yes, this was using the latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants