feat(linter): update allowed ESLint config file extensions

[TorinFrancis]

ESLint added experimental support for typescript config files since 9.9.0, and as of 9.18.0 that support is stable. This PR add ts/mts/cts to the list of known eslint config files, and adds the same extensions to config file generators

Current Behavior

When using the eslint executor with a ts file, returns error "When using the new Flat Config with ESLint, all configs must be named eslint.config.js or eslint.config.cjs and .eslintrc files may not be used. See https://eslint.org/docs/latest/use/configure/configuration-files"

When using the eslint plugin, the inferred task is not created for projects that do not have a non-ts eslint config.

Workarounds

• Compiling ts rules/configs in a project. Introduces other issues
• Using jiti or comparable
• For plugin users, having a fake eslint.config.js at the root allows the inferred task to be created. ESLint will still use the ts config.
  • Cache targets are wrong
  • Complications in non-monorepo workspaces

Expected Behavior

When using the eslint executor with a ts file, no error is thrown.

When using the eslint plugin with a ts file, the inferred task is created.

Related Issue(s)

No issues, but addresses this discussion

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Feb 25, 2025 7:06pm

[TorinFrancis]

Hey @leosvelperez is there anything I can do to help get this through? This is my first Nx PR so I'm sure I've missed some things