2.10 parse error
See original GitHub issueWhat version of ESLint are you using?
2.10
What parser (default, Babel-ESLint, etc.) are you using?
Tried both default and babel-eslint
Please show your full configuration:
{
"extends": "ember",
"parser": "babel-eslint",
"ecmaFeatures": {
modules: true,
blockBindings: true,
arrowFunctions: true,
objectLiteralShorthandMethods: true,
objectLiteralShorthandProperties: true,
templateStrings: true
},
"rules": {
"quote-props": [2, "consistent-as-needed"],
"no-ternary": 0,
"newline-per-chained-call": 0,
"arrow-body-style": 0,
"no-warning-comments": 0,
"max-len": [1, 200],
"camelcase": 0,
"space-before-function-paren": [1, "never"],
"one-var": [ 1, "never" ],
"indent": [2, 2, {SwitchCase: 1}],
"object-shorthand": [ 2, "always" ],
"prefer-const": 0,
"comma-dangle": 0,
"spaced-comment": 1,
"object-curly-spacing": 0,
"arrow-spacing": [ 1, {
before: true,
after: true
} ],
"no-restricted-syntax": 0,
"no-console": 0,
"no-magic-numbers": 0,
"valid-jsdoc": [2, {
"requireReturn": false
}]
},
"globals": {
"Ember": true,
"$": true,
"Edgar": true,
"visit": true,
"andThen": true,
"find": true,
"findWithAssert": true,
"click": true,
"triggerEvent": true,
"wait": true,
"ok": true,
"equal": true,
"notEqual": true,
"deepEqual": true,
"strictEqual": true,
"throws": true,
"fillIn": true,
"exists": true,
"currentPath": true,
"currentURL": true,
"currentRouteName": true,
"breadcrumbValidator": true,
"renderProfiler": true,
"expect": true,
"_": true,
"test": true,
"module": true,
"YAMP": true,
"App": true
}
}
What did you do? Please include the actual source code causing the issue.
test('Create New Rule', async function() {
});
What did you expect to happen?
No parse error
What actually happened? Please include the actual, raw output from ESLint.
/Workspace/tests/acceptance/rule-test.js
1:31 error Parsing error: Unexpected token function
Issue Analytics
- State:
- Created 7 years ago
- Reactions:16
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Getting a Parsing error in files - Gimp-Forum.net
Hi all, I installed a bunch of new brushes, patterns and gradients, but they don't show up when I open up GIMP (2.10),...
Read more >Fatal Parse Error when trying to load new pattern - GitLab
Receive same error message when attempting to paste a smaller image as new pattern. GIMP Version:2.10.22 Operating System: Windows 10 Package: ...
Read more >parse-error / F0010 - Pylint 2.16.0-dev documentation
parse-error / F0010# ... Description: Used when an exception occurred while building the Astroid representation which could be handled by astroid. Correct code:...
Read more >Error editing with gimp 2.10.8 a .xcf from gimp 2.10.14-2
on Ubuntu Eoan editing with gimp 2.10.8 a .xcf from Ubuntu 20.4 gimp ... expected number (float) - fatal parse error ProblemType: Bug ......
Read more >Parse error: unexpected identifier `taNewMessage
Parse error: unexpected identifier `taNewMessage ' ... Centos 7, Pidgin 2.10.11-9.el7 (libpurple 2.10.11), using Facebook. Is there an actual bug ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry about this. We have a plan to release v2.10.1 within this weekend or Monday. (edit)
The mistake is here: https://github.com/eslint/eslint/pull/6108/files#diff-f7bf2b665273dfa66ffa4ad7c0a52bb9R252
parser
orparserOptions
shouldn’t be provided in that object literal if they are null or undefined.