You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
As I code, I frequently get Parsing Error: Unexpected token, expected "}" (fatal). This error makes sense if I haven't closed a closure, etc. The issue is even after I complete my closure, the error persists. Running the eslint cli shows no errors, and closing and reopening the file clears the error. This is a recent problem.. my guess is eslint is overwhelmed with linting files, however I'm not sure how to debug that. There doesn't seem to be a way to "re-lint" as a way to check.
E.g.
import {
Wait a second, lint error shows up.
import map from 'lodash/map';
Error still says unexpected token. Running eslint cli shows no error. Close file, open file, error disappears.
I've noticed even after I close a file, the atom lint status still shows that file under "Current"
Bug Checklist
Restart Atom
Verify the eslint CLI gives the proper result, while linter-eslint does not
Paste the output of the Linter Eslint: Debug command from the Command Palette below
Atom version: 1.28.2
linter-eslint version: 8.4.1
ESLint version: 3.3.0
Hours since last Atom restart: 9.7
Platform: darwin
Using local project ESLint from: /srv/nerdwallet/react-local-dev/packages/my-nerdwallet/node_modules/eslint
Current file's scopes: [
"source.js.jsx",
"meta.class.js",
"entity.other.inherited-class.js"
]
linter-eslint configuration: {
"fixOnSave": true,
"lintHtmlFiles": false,
"useGlobalEslint": false,
"showRuleIdInMessage": true,
"disableWhenNoEslintConfig": true,
"eslintrcPath": "",
"globalNodePath": "",
"advancedLocalNodeModules": "",
"eslintRulesDirs": [],
"disableEslintIgnore": false,
"disableFSCache": false,
"scopes": [
"source.js",
"source.jsx",
"source.js.jsx",
"source.babel",
"source.js-semantic"
],
"rulesToSilenceWhileTyping": [],
"rulesToDisableWhileFixing": [],
"ignoreFixableRulesWhileTyping": false
}
Issue Type
Bug
Issue Description
As I code, I frequently get
Parsing Error: Unexpected token, expected "}" (fatal)
. This error makes sense if I haven't closed a closure, etc. The issue is even after I complete my closure, the error persists. Running theeslint
cli shows no errors, and closing and reopening the file clears the error. This is a recent problem.. my guess is eslint is overwhelmed with linting files, however I'm not sure how to debug that. There doesn't seem to be a way to "re-lint" as a way to check.E.g.
Wait a second, lint error shows up.
Error still says unexpected token. Running eslint cli shows no error. Close file, open file, error disappears.
I've noticed even after I close a file, the atom lint status still shows that file under "Current"
Bug Checklist
eslint
CLI gives the proper result, whilelinter-eslint
does notLinter Eslint: Debug
command from the Command Palette below.eslintrc
The text was updated successfully, but these errors were encountered: