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

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

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”
}
}

Solutions/Answers:

Solution 1:

Add this to the root of your .eslintrc

"parser": "babel-eslint"

Or if you wish not change the parser:

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

Solution 2:

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

Related:  Plugin throwing TypeError after WordPress 4.5 update

Solution 3:

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

Solution 4:

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

Solution 5:

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

References