Replies: 2 comments
-
Hi @sumleo, thanks for the issue! Can you please share your configuration? This is a correct parsing error in modules, as top-level functions in modules cannot be redeclared. It works in chrome console since it's parsed as a script. Online demo with sourceType: "module" (parsing error) Online demo with sourceType: "script" (no parsing error) |
Beta Was this translation helpful? Give feedback.
-
Hi @sumleo, thanks for the issue. It looks like there's not enough information for us to know how to help you. If you're reporting a bug, please be sure to include:
Requesting a new rule? Please see Proposing a New Rule for instructions. Requesting a rule change? Please see Proposing a Rule Change for instructions. If it's something else, please just provide as much additional information as possible. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Tell us about your environment
Node version: v14.12.0
npm version: v6.14.8
Local ESLint version: Not found
Global ESLint version: v7.13.0 (Currently used)
What parser (default,
@babel/eslint-parser
,@typescript-eslint/parser
, etc.) are you using?default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
What did you expect to happen?
No errors while parsing it (Try it with chrome console)
What actually happened? Please include the actual, raw output from ESLint.
/Users/test/index/test.js
3:10 error Parsing error: Identifier 't' has already been declared
✖ 1 problem (1 error, 0 warnings)
Are you willing to submit a pull request to fix this bug?
Beta Was this translation helpful? Give feedback.
All reactions