The keyword const is reserved как исправить

Bug: Parsing error: The keyword ‘const’ is reserved #16174

<>’s edit

Environment

Node version: 16.5.0
yarn version: 1.22.10
Local ESLint version: latest
Global ESLint version: latest
Operating System: Widnows

What parser are you using?

What did you do?

What did you expect to happen?

it’s supposed to lint a string that looks like this :

What actually happened?

I received this error:

Participation

• I am willing to submit a pull request for this issue.

Beta Was this translation helpful? Give feedback.

1 You must be logged in to vote

the default ecmaVersion is 5, you’ll need to config it >=6, to use the features like let/const .

the default ecmaVersion is 5, you’ll need to config it >=6, to use the features like let/const .

Beta Was this translation helpful? Give feedback.

Marked as answer

1 You must be logged in to vote

Converted from issue

This discussion was converted from issue #16172 on August 01, 2022 21:44.

Add heading text

Add italic text,

Insert Link

Add a bulleted list,

Add a numbered list,

Add a task list,

Directly mention a user or team

Reference an issue or pull request

Add heading text

Add italic text,

Add a bulleted list,

Add a numbered list,

Add a task list,

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

eslint errors on ‘interface’ keyword even when using this parser #620

I have Babel, ESLint, and Flow all being used in my React Native project. My .eslintrc looks like this:

For some reason, I’m getting an error when I try to declare an interface type in my code:

Not sure why. Could I have setup something wrong?

The text was updated successfully, but these errors were encountered:

Hi @jamesqo, Did you find any solution for this issue?
I got a similar error message.

Eslint version: v5.4.0

@AntonioTsai @jamesqo Did you find out?

I think this is expected behavior. It doesn’t look like Flow supports default exports of types or interfaces. See the bottom of this page for more details.

You can still export the interface, it just has to be named.

It is a reserved keyword, but one who uses Typescript. What’s the solution esp. when eslint runs on pre-commit.

From the documentation linked above it looks like export default interface <> isn’t valid Flow syntax, and so can’t be used with Flow. You’re correct that it is valid in TypeScript though (see microsoft/TypeScript@5ef6192).

I believe the easiest workaround would be to export the interface as a named export.

Thank you for the issue. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

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.

Источник

ERROR: Parsing error: The keyword ‘const’ is reserved #14966

Prerequisites

• [ yes] Can you reproduce the problem with Debug -> Reload Without Extensions ?
• [yes] Did you perform a cursory search to see if your bug or enhancement is already reported?
• [yes ] Did you read the Troubleshooting guide?
  I change the «brackets-eslint.useLocalESLint»: false, to true in preferences as suggested here:

Expected an identifier and instead saw ‘const’ — Stopping (. % scanned) #11632
Then restarted brackets

For more information on how to write a good bug report read here
For more information on how to contribute read here

Description

ERROR: Parsing error: The keyword ‘const’ is reserved
[Description of the bug or feature]
Unable to continue

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on. ]

Expected behavior: [What you expected to happen]
No error
Actual behavior: [What actually happened]
ERROR: Parsing error: The keyword ‘const’ is reserved const = require (‘electron’)

Versions

Please include the OS and what version of the OS you’re running.
Ubuntu 18.04 with xubuntu desktop
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)
Release 1.14 build 1.14.0-17740 (release 329d08f)

The text was updated successfully, but these errors were encountered:

Источник

Parsing error: The keyword ‘const’ is reserved #28

Not sure why but somehow it started giving me this error.
I have es6: true in my .eslintrc.js
Running eslint from command line works fine and setting env inline in the file also works

any ideas on how to fix or debug?
I tried: reinstall (hence how I found the registry error ;)), using root: true , using old .eslintrc

The text was updated successfully, but these errors were encountered:

@AdriVanHoudt if brackets-eslint founds an eslint in your project (https://github.com/zaggino/brackets-eslint/blob/master/domain.js#L62) then it’ll use that version and version installed by npm-registry won’t matter. Check your project if you don’t have an old version of eslint maybe?

it is missing the config file? (version is fine btw)

When useEslintrc: true you shouldn’t need to specify path to config file. I use this extension across about 8-10 projects daily with different configs and it works fine, most of them use const too. But feel free to experiment, maybe you ran into some edge case or something.

yeah I have used it too across many different projects, it somehow broke for some reason 🙁

If I check here: http://eslint.org/docs/user-guide/configuring
With latest eslint, it should be «ecmaVersion»: 6, and not es6: true ?

Does your project work fine if you check it using eslint 2.7.0 from command line? Without Brackets?

es6: true is still a thing, tried with ecmaVersion but no difference, I made a new js file and it does not lint with my config at all

yes it works with running eslint . in project root

I’m guessing it’s not something you have lying around publicly on github? 🙂

the project or config?

also switched to another project with it’s own eslintrc and that uses const and no error, switch back, const error gone but now complains about default rules (like indents), owke.

well, the whole repo with config . or at least a config with a file which replicates the problem when I fetch it

Источник

Parsing error: The keyword ‘export’ is reserved #1464

What code were you trying to parse?

I’m trying to use typescript-eslint , and I followed the Getting Started page. Unfortunately, I’m having problems to make the parser identify very basic TypeScript/JS keywords, like export .

Please see https://github.com/flisboac/ts-promise-scheduler for the project in question. The error is:

My .eslint.js is configured as such:

And here are the first lines of the affected file

What did you expect to happen?

To accept export as a keyword, as per named/default export in TypeScript and the ES6+ standards, in the context of exporting declarations.

What actually happened?

export seems to be identified as a reserved name, regardless of context. Parsing fails.

Versions

Disclaimer:I’m using yarn .

Output of yarn versions`:

Output of yarn list :

The text was updated successfully, but these errors were encountered:

Источник

error  Parsing error: The keyword 'const' is reserved

const express = require('express');
const app = express();
const _ = require('underscore');

6 ответов

Лучший ответ

{
    "parserOptions": {
        "ecmaVersion": 2017
    },

    "env": {
        "es6": true
    }
}

/* eslint-env es6 */
/* eslint-disable no-console */

/* eslint-env es6 */
/* eslint-disable */

const newComment = {
    dishId: dishId,
    rating: rating,
    author: author,
    comment: comment
};
newComment.date = new Date().toISOString();

"env": {
"browser": true,
"node": true,
"es6": true
},

...

"eslint.options": {
    "useEslintrc": false,
    "parserOptions": {
        "ecmaVersion": 2017
    },
    "env": {
        "es6": true
    }
}

module.exports = {
    "parserOptions": {
        "ecmaVersion": 6
    }
};