New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SUPPORTED_TYPESCRIPT_VERSIONS #2066
Comments
Hi! Thank you for this project! Hopefully this information is of assistance. I believe this issue presents to me like this:
eslint related packages:
Began happening after this upgrade: diff --git a/package.json b/package.json
index e8bb660..d336448 100644
--- a/package.json
+++ b/package.json
@@ -12,7 +12,7 @@
"@mdx-js/react": "^1.6.4",
"emotion-theming": "^10.0.27",
"flexsearch": "^0.6.32",
- "gatsby": "^2.22.4",
+ "gatsby": "^2.22.6",
"gatsby-image": "^2.4.5",
"gatsby-plugin-catch-links": "^2.3.2",
"gatsby-plugin-chakra-ui": "^0.1.4",
@@ -45,12 +45,12 @@
},
"devDependencies": {
"@types/moment-duration-format": "^2.2.2",
- "@types/node": "^14.0.4",
+ "@types/node": "^14.0.5",
"@types/react": "^16.9.35",
"@types/react-dom": "^16.9.8",
"@types/react-helmet": "^6.0.0",
- "@typescript-eslint/eslint-plugin": "^2.34.0",
- "@typescript-eslint/parser": "^2.34.0",
+ "@typescript-eslint/eslint-plugin": "^3.0.0",
+ "@typescript-eslint/parser": "^3.0.0",
"eslint-config-prettier": "^6.11.0",
"eslint-loader": "^4.0.2",
"eslint-plugin-prettier": "^3.1.3", |
Just adding to this issue. Upgrading to 3.0.0 breaks VSCode integration. Likely, because of the error above (unsupported version), but VSCode doesn't know that, so you just get hundreds of lint errors instead, for code that worked fine yesterday. Running eslint on the command-line shows the SUPPORTED warning, which explains why VSCode is failing, but it isn't obvious from the IDE itself. Downgrading to 2.34 fixes it, so I'll stay at that release for now. |
The reason it isn't working with the release, but is correct in master is because it's been fixed in master. See #2057 This will be released on monday morning as part of our standard release cycle. You can also consider using our |
yes I know you hate such types of bugs but still
so here you have
typescript-eslint/packages/typescript-estree/src/parser.ts
Line 23 in 5eedbff
good range which I like
but if i do
i see another range which is outdated and i believe was fixed some time ago because in 2.x.x it works fine
at the same time package.json in GH and in my local node_module shows same version 3.0.0
The text was updated successfully, but these errors were encountered: