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" }
}15 Answers
Add this to the root of your .eslintrc.json (formerly .eslintrc)
"parser": "babel-eslint"and make sure to run:
npm install babel-eslint --save-devThe 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:
2The problem was i had installed eslint globally and locally, causing inconsistencies in SublimeLinter-contrib-eslint. I uninstalled eslint globally and SublimeLinter is working.
2Closing VS code and re-open it does the trick for me...
1Not 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.
5The currently highest voted answer works. However, it 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",
};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:
1This 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 } }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", };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.jsRestart 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.
Adding ecmaVersion to .eslintrc.json fixed the issue
{ "ecmaVersion": 2015, "extends": [ "eslint:recommended", "plugin:react/recommended" ]
}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.
I have been facing this error on next.js 13 today and my eslint file looks like this:
{ "root": true, "settings": { "react": { "version": "detect" }, "env": { "browser": true, "node": true, "es2020": true, "jest": true }, "extends": [ "eslint:recommended", "plugin:react/recommended", "plugin:react-hooks/recommended", "plugin:@typescript-eslint/recommended", "plugin:prettier/recommended" ], "parser": "@typescript-eslint/parser", "parserOptions": { "ecmaVersion": "latest", "sourceType": "module", "ecmaFeatures": { "jsx": true } }, "plugins": ["react", "react-hooks", "@typescript-eslint"], "rules": {} }
}So I removed this piece of code and it works fine:
"settings": { "react": { "version": "detect" }ESlint the disabling rules in .eslintrc.json file.
{ "extends": "next", "rules": { "react/no-unescaped-entities": "off", "@next/next/no-page-custom-font": "off" }
}For me VSCode the eslint extension had a problem and after disabling it for current workspace it worked
