Parsing Error The Keyword import is Reserved (SublimeLinter-contrib-eslint)

Question

I have a problem with eslint, it gives me [Parsing Error The keyword import is reserve] this is only occur in sublime, in atom editor work well. I have eslint

.eslintrc.js

module.exports = {
    "extends": "airbnb",
    "plugins": [
        "react"
    ]
};

package.json

{
  "name": "paint",
  "version": "0.0.0",
  "description": "paint on the browser",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [
    "paint",
    "javascript"
  ],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "browserify": "^11.2.0",
    "eslint": "^2.2.0",
    "eslint-config-airbnb": "^2.1.1",
    "eslint-plugin-react": "^3.11.2",
    "gulp-babel": "^5.2.1",
    "gulp-clean": "^0.3.1",
    "gulp-stylus": "^2.2.0",
    "vinyl-source-stream": "^1.1.0"
  }
}

score 241 · Answer 1 · edited Feb 22 '22 at 14:25

241

Add this to the root of your .eslintrc.json (formerly .eslintrc)

"parser": "babel-eslint"

and make sure to run:

npm install babel-eslint --save-dev

edited Feb 22 '22 at 14:25

Henke

4,445
3
31
44

answered Dec 16 '16 at 18:18

Iman Mohamadi

6,552
3
34
33

17

This worked for me too, thanks. If it helps anyone, my entire .eslint file is `{"parser": "babel-eslint"}` – Mark Madej Jul 26 '17 at 04:12
For me, the file had to be _renamed_ to `.eslintrc` with its contents `{"parser" : "babel-eslint"}` – Aakash Sep 26 '18 at 07:39
16

No need to change the parser. Doing `"parserOptions": { "sourceType": "module" }` is enough – nathancahill Oct 31 '18 at 01:23
@nathancahill Thanks. But are there other more general benefits of babel-eslint? – Ashley Aitken Apr 27 '20 at 03:39
`{ "parser": "babel-eslint" }` worked for me with TypeScript and Gatsby in the `gatsby-browser` file – PhillyStafford Oct 17 '20 at 23:03
9

As of July-2021, { "parser": "@babel/eslint-parser" } – JustinC Jul 21 '21 at 16:50
5

But why does adding `babel-eslint` work? Just setting parseOptions/sourceType to "module" is not enough according to what I experience. – bytrangle Jul 25 '22 at 10:49
2

sourceType 'module' is not supported when ecmaVersion < 2015. Adding `"ecmaVersion": 6` may be also necessary. – josemigallas Jun 13 '23 at 09:09
`"ecmaVersion": "latest" ` was helpful for me -- though probably not suited for all. – alphazwest Jul 28 '23 at 23:10

score 97 · Answer 2 · edited Oct 31 '18 at 01:37

97

The eslint option that solves the "The keyword import is reserved" error is parserOptions.sourceType. Setting it to "module" allows the import keyword to be used.

.eslintrc

{
    "parserOptions": {
        "sourceType": "module"
    }
}

Docs: https://eslint.org/docs/user-guide/configuring#specifying-parser-options

edited Oct 31 '18 at 01:37

nathancahill

10,452
9
51
91

answered Jul 21 '17 at 06:33

1

Additionally, although I do not use babel, `npm install babel-eslint --save-dev` and `parser: 'babel-eslint'` were needed to get rid of the 'import is reserved' error. It is [not a good solution](https://github.com/eslint/eslint/issues/11189#issuecomment-446646882) but a workaround [recommended by eslint for now](https://github.com/eslint/eslint/issues/11486). – Akseli Palén Feb 02 '21 at 22:21
5

Yes, but I also had to add `"ecmaVersion": "latest"` under `parserOptions`. – Michael Cox Dec 15 '22 at 21:44

score 19 · Accepted Answer · answered Mar 25 '16 at 04:59

19

The problem was i had installed eslint globally and locally, causing inconsistencies in SublimeLinter-contrib-eslint. I uninstalled eslint globally and SublimeLinter is working.

answered Mar 25 '16 at 04:59

pedro luis

1,545
2
10
8

Thanks for this. IMO this problem may more universal that just SublimeLinter. – Matt Jensen Oct 28 '16 at 20:24
Stems from module-type syntax. CommonJS module uses 'require'. – Stephen W. Wright Jun 17 '17 at 04:13

score 14 · Answer 4 · answered May 23 '20 at 21:36

14

Closing VS code and re-open it does the trick for me...

answered May 23 '20 at 21:36

JulienRioux

2,853
2
24
37

The same solved the problem with WebStorm – Tatyana Molchanova Jun 20 '22 at 08:21

score 7 · Answer 5 · answered Mar 20 '16 at 09:26

7

Not sure about it but try to rename your file to .eslintrc and just use

{
  "extends": "airbnb",
  "plugins": ["react"]
};

Also be sure you have the required packages installed. github.com/airbnb/javascript

answered Mar 20 '16 at 09:26

the

99
3

1

I solved the error, the problem was i had eslint globally and locally. Thanks – pedro luis Mar 25 '16 at 04:46
2

Oddly the `.eslintrc.js` to `.eslintrc` fixed it for me, weird. Thanks! – JREAM Dec 29 '18 at 17:56
jfyi - This din't work for VS Code, with or without global eslint installation. – Manohar Reddy Poreddy Apr 30 '20 at 05:29
I spent a while on this before realizing that I'd named my file `eslintrc.js` and not `.eslintrc.js` (no leading dot). – danvk Feb 13 '22 at 16:06
Renaming `.eslintrc.js` to `.eslintrc.cjs` worked for me. – John Y Oct 03 '22 at 15:55

Crisoforo Gaspar · Answer 6 · 2021-10-31T19:16:30.737

7

The accepted answer works, however, is no longer under maintenance and the newly suggested approach is to use the version from the mono repo instead.

Installation

$ npm install eslint @babel/core @babel/eslint-parser --save-dev
# or
$ yarn add eslint @babel/core @babel/eslint-parser -D

.eslintrc.js

module.exports = {
  parser: "@babel/eslint-parser",
};

Reference

edited Oct 31 '21 at 19:16

answered Aug 16 '21 at 20:58

Crisoforo Gaspar

3,740
2
21
27

score 3 · Answer 7 · answered Feb 24 '17 at 09:12

3

i also got this error in a meteor project and i could solved it setting sourceType to "module" more details can be found in Eslint docs: http://eslint.org/docs/user-guide/configuring#specifying-parser-options

answered Feb 24 '17 at 09:12

SPM

31
3

jfyi - This din't work for VS Code, copy pasted in parserOptions > sourceType. – Manohar Reddy Poreddy Apr 30 '20 at 05:33

score 3 · Answer 8 · answered Dec 23 '19 at 05:50

This config worked for me. (I am using create-react-app but applicable to any eslint project)

.eslintrc (create file in root if it doesnt exist)

{
    "rules": {
      "jsx-a11y/anchor-is-valid": [ "error", {
        "components": [ "Link" ],
        "specialLink": [ "to" ]
      }]
    },
    "parserOptions": {
        "sourceType": "module",
        "ecmaVersion": 2015
    }
  }

score 2 · Answer 9 · answered Aug 24 '21 at 15:27

The same issue occurred when creating js files within a typescript react-native project while eslint is enabled.

Changing the file type from js to ts resolved the issue.

Also, adding the .eslintrc.js file as mentioned in previous answers resolved the issue without changing the file type from js to ts.

       module.exports = {
          parser: "@babel/eslint-parser",
       };

score 2 · Answer 10 · edited Aug 03 '22 at 07:49

The issue is seen with the new react app, and in Visual Studio Code, even at this time - August 2022

Create a file .eslintrc.js in the root folder Paste the below contents in .eslintrc.js Restart your editor, like VS Code. Now I can see real errors, instead of those fake import/export errors. .eslintrc.js file contents:

   export const parser = "@babel/eslint-parser";

The accepted answer works, however, the newly suggested approach is to use the version from ES6.

score 1 · Answer 11 · edited Sep 21 '22 at 20:13

1

I found this issue while creating the vue project (Used Editor: Visual Code)

Install babel-eslint package

npm install babel-eslint

Create the .eslintrc.js file and add below code

module.exports = {
    root: true,
    parserOptions: {
        'sourceType': 'module',
        parser: 'babel-eslint'   
    }
}

npm run serve, that error will be resolved like magic.

edited Sep 21 '22 at 20:13

Sreekumar P

5,900
11
57
82

answered Mar 16 '20 at 00:47

Bhupinder

11
2

OR, try without 'sourceType' module.exports = { root: true, parserOptions: { parser: 'babel-eslint' } } – Bhupinder Mar 16 '20 at 01:08

score 1 · Answer 12 · answered Oct 07 '21 at 05:01

1

Adding ecmaVersion to .eslintrc.json fixed the issue

{
    "ecmaVersion": 2015,
    "extends": [
        "eslint:recommended",
        "plugin:react/recommended"
    ]
}

answered Oct 07 '21 at 05:01

Gvs Akhil

2,165
2
16
33

score 0 · Answer 13 · answered Jul 11 '23 at 10:27

0

ESlint the disabling rules in .eslintrc.json file.

  {
  "extends": "next",
  "rules": {
    "react/no-unescaped-entities": "off",
    "@next/next/no-page-custom-font": "off"
  }
}

answered Jul 11 '23 at 10:27

Apurv

21
5

Parsing Error The Keyword import is Reserved (SublimeLinter-contrib-eslint)

13 Answers13

Linked