V8 is ready for public testing (hooray!https://typescript-eslint.io/blog/announcing-typescript-eslint-v8-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 v8 beta in front of many people(think >1000 GH stars)

I'm thinking to start, at least:

• Angular:(blocked onInternal repo tooling: use ESLint instead of the deprecated TSLint angular/angular#56562)
• Astro:chore: use typescript-eslint@v8's projectService for typed linting withastro/astro#11315
• Babel:Update typescript-eslint v8 babel/babel#16557
• create-t3-app:chore: bump typescript-eslint to v8 t3-oss/create-t3-app#1936
• Docusaurus:(blocked onchore: bump typescript-eslint to v7 facebook/docusaurus#10271)
• Prettier:Updatetypescript-eslint to v8 prettier/prettier#16333
• Redwood:chore: brought in typescript-eslint@v8 with stylistic preset redwoodjs/graphql#10911
• Sveltekit:feat: upgrade eslint to v9 sveltejs/kit#12268
• Tanstack:(blocked onShould use standard '@typescript-eslint/' prefix for rule names, not 'ts/' TanStack/config#115)
• trpc:chore: bump typescript-eslint to v8 with project service trpc/trpc#5868
• Vite:chore: bump typescript-eslint to v8 vitejs/vite#17624

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 8.0.0 #8914)?

Filing this tracking issue to make sure we do this before releasing v8 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.

For reference, v6's equivalent beta issue:#6760