@typescript-eslint/parser has stopped working
See original GitHub issueDescribe the bug
Viewing the AST generated by @typescript-eslint/parser
is no longer possible. It worked a couple weeks ago.
To Reproduce Steps to reproduce the behavior:
- Go to https://astexplorer.net/
- For the parser choose
@typescript-eslint/parser
- Observe that the tree doesn’t update, and if you open the console there’s an error loading the parser
Expected behavior
@typescript-eslint/parser
loads and updates the tree
Screenshots
Browser (please complete the following information):
- OS: Mac OS 10.15.5
- Browser: Chrome
- Version: 84.0.4147.89 (Also repros with any other browser and OS I tried, including in incognito mode to ensure there’s not a problem with any cached stuff)
astexplorer settings:
- Selected parser:
@typescript-eslint/parser
- Selected transformer (if applicable): none
- Contents of the local storage key
explorerSettingsV1
(code can be removed if you don’t want it to be public)
{
"showTransformPanel": false,
"parserSettings": {},
"parserPerCategory": {
"javascript": "acorn"
},
"workbench": {
"parser": "acorn",
"code": "/**\n * Paste or drop some JavaScript here and explore\n * the syntax tree created by chosen parser.\n * You can use all the cool new features from ES6\n * and even more. Enjoy!\n */\n\nlet tips = [\n \"Click on any AST node with a '+' to expand it\",\n\n \"Hovering over a node highlights the \\\n corresponding location in the source code\",\n\n \"Shift click on an AST node to expand the whole subtree\"\n];\n\nfunction printTips() {\n tips.forEach((tip, i) => console.log(`Tip ${i}:` + tip));\n}\n",
"keyMap": "default",
"transform": {
"code": "",
"transformer": null
}
}
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Eslint not working with the TypeScript syntax - Stack Overflow
It's not a Typescript error; the Typescript code is correct. The problem is that ESLint doesn't recognise the Typescript syntax. – kaya3.
Read more >@typescript-eslint/parser - npm
An ESLint parser which leverages TypeScript ESTree to allow for ESLint to lint TypeScript source code. NPM Version NPM Downloads. See https ...
Read more >"ParserOptions.project" has been set for @typescript-eslint ...
The error 'Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser' occurs when we try to lint files that aren't included in our ...
Read more >parseroptions.project has been set for @typescript-eslint/parser
// DO NOT SET createDefaultProgram to true to prevent future breakage. Create a new tsconfig.eslint.json Add .eslintrc in .eslintignore Ensure that ONLY the ......
Read more >How to use ESLint with TypeScript | Khalil Stemmler
You may have also heard of TSLint, the TypeScript equivalent. In 2019, the team behind TSLint decided that they would no longer support...
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
Looks like we are somehow replacing a module that some part of typescript-eslint depends on. I have tried to tweak the webpack configuration but haven’t been successful yet. I’ll keep trying.
It should work again as of d0d46179a0014ee2826d38cb81b9867de3fbfd0a (already deployed) . Please let me know if it doesn’t.