Closed
Description
V6 is ready for public testing (hooray! https://typescript-eslint.io/blog/announcing-typescript-eslint-v6-beta 🎉) and we want to make sure we try it out on lots of projects. It'd be particularly valuable to try out projects that are:
- Large enough to exercise test cases (think >100 source files)
- Popular enough to get visibility for the v6 beta in front of many people (think >1000 GH stars)
I'm thinking to start, at least:
Angular(still on TSLint)- Astro: feat: use typescript-eslint@v6's reworked configs withastro/astro#7425
- Babel: chore: Use
typescript-eslint@v6
with reworked configs babel/babel#15716 - create-t3-app: feat: typescript-eslint@v6 t3-oss/create-t3-app#1476
Prettier(doesn't use our recommended configs)- Redux: build: use typescript-eslint@v6 internally reduxjs/redux#4566
- Redux Toolkit: build: use typescript-eslint@v6 internally reduxjs/redux-toolkit#3541
Solid(doesn't lint itself)- Tanstack (was on my home computer and I had a hard time setting up before traveling - next time maybe!)
- trpc: chore: use typescript-eslint@v6 with reworked configs trpc/trpc#4541
- TypeScript: Updated typescript-eslint to v6 microsoft/TypeScript#54693
For each of these projects, we should see:
- Is someone on their end willing to try things out?
- In addition to version bumps, are they up for recreating their linter configs with the new configs (Changes to configurations for 6.0.0 #6014)?
Filing this tracking issue to make sure we do this before releasing v6 as stable.
If you've got a project that matches those criteria & want to get it added to the list, let us know! We'd be happy to work with you.