"unexpected token import" error while running tests

Question

when I run the test, I get the following error:

({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import React from 'react';
                                                                                         ^^^^^^

SyntaxError: Unexpected token import

It makes sense, since all the lines of "import React" or "import Enzyme", are marked as an error by ESlint. I don´t know why.

This is my .babelrc file:

{
  "presets": [
    "react",
    "stage-2",
    ["env", {
      "test": {
        "presets": ["env", "react", "stage-2"],
        "plugins": ["transform-export-extensions"],
        "only": [
          "./**/*.js",
          "node_modules/jest-runtime"
        ]
      },
      "targets": {
        "browsers": ["last 2 versions", "safari >= 7"]
      },
      "modules": false
    }]
  ]
}

Are babel transpiling your code? – jmargolisvt Mar 16 '18 at 19:56 — jmargolisvt, Mar 16 '18 at 19:56
I think so. I added my .babelrc configuration – Iván Mar 16 '18 at 20:01 — Iván, Mar 16 '18 at 20:01

score 3 · Answer 1 · edited May 08 '19 at 11:06

If you are using babel 6 and jest 24 then be informed that jest 24 has dropped support for babel 6.

There are two solutions

Upgrade your app to babel 7. (actively maintained by its developers)
If you don't want to upgrade, make sure that you stick on jest 23.

There is one more work around if you want to use jest 24. Use babel-jest locked at version 23.

"dependencies": {
  "babel-core": "^6.26.3",
  "babel-jest": "^23.6.0",
  "babel-preset-env": "^1.7.0",
  "jest": "^24.0.0"
}

score 0 · Answer 2 · answered Mar 16 '18 at 21:00

0

Hello dev can you try,

install babel-jest

set this inside .babelrc

  "env": {
    "test": {
    "presets": ["es2015", "react"],
    "plugins": ["syntax-object-rest-spread", "transform-es2015-modules-commonjs"]      
  },

testing with jest

answered Mar 16 '18 at 21:00

Angel

1,670
1
11
14

did you set the env property in the .babelrc? – Angel Mar 16 '18 at 23:33

"unexpected token import" error while running tests

2 Answers2