Questions regarding @typescript-eslint/eslint-plugin & @typescript-eslint/eslint-parser updates

[hzhu]

Summary

I noticed that there are only Renovate PRs opened for minor versions of @typescript-eslint/eslint-plugin and @typescript-eslint/eslint-parser, e.g. #27080.

It seems like a requirement to use the latest versions of @typescript-eslint/eslint-plugin and @typescript-eslint/eslint-parser require project dependencies (such as Gatsby?) to be up-to-date with v4 at least. We've a project that indicates Gatsby might be the reason we aren't able to upgrade @typescript-eslint/eslint-plugin to v4.

Questions

Does Gatsby plan on updating major versions of @typescript-eslint/eslint-plugin and @typescript-eslint/eslint-parser?

[LekoArts]

Seems like Gatsby is not at fault? zendeskgarden/react-components#871 (comment)

[hzhu]

Hi @LekoArts 👋

I pointed to the incorrect link earlier. It should have pointed here instead: zendeskgarden/website#184 (review)

[LekoArts]

Ok, I see. We'll have to look into the breaking changes for the major change. In the meantime you can force the version by using yarn resolutions: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

[hzhu]

Awesome, that sounds great. Yarn's resolution should work in the meantime. Thank you! 🙏

[ROHIT498]

I have the same problem, although it's for all files.

$ yarn list --pattern "typescript"
yarn list v1.22.4
├─ @babel/plugin-syntax-typescript@7.8.3
├─ @babel/plugin-transform-typescript@7.8.3
├─ @babel/preset-typescript@7.8.3
├─ @typescript-eslint/eslint-plugin@2.24.0
├─ @typescript-eslint/experimental-utils@2.24.0
├─ @typescript-eslint/parser@2.24.0
├─ @typescript-eslint/typescript-estree@2.24.0
├─ typescript-tslint-plugin@0.5.5
└─ typescript@3.8.3
VSCode Eslint version: 2.1.1

module.exports = {
root: true,
parser: '@typescript-eslint/parser',
plugins: [
'@typescript-eslint',
],
parserOptions: {
tsconfigRootDir: __dirname,
project: ['./tsconfig.json'],
},
extends: [
'eslint:recommended',
'plugin:@typescript-eslint/eslint-recommended',
'plugin:@typescript-eslint/recommended',
'plugin:@typescript-eslint/recommended-requiring-type-checking',
],
};
Do you know how the vscode plugin watches for changes and adds new files to compilation context ? I feel that’s where the issue is.

This issue is happening for our whole team currently across VSCode and Atom IDEs. Our only solution has been to remove node_modules and reinstall all packages. It usually happens when pulling in new files from Git.

[hzhu]

I have the same problem

Does your project use Gatsby? How come it isn't listed in your yarn list tree? It doesn't seem like the same problem as this issue.

[ROHIT498]

Ya but i have provided to just give an idea of using yarn

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜