Create Next-Generation JS/TS Linting Packages

[kevinfodness]

Description

Given that ESLint has changed focus to be primarily about performance, security, accessibility, and best practices, and Prettier has emerged as the tool of choice for formatting, we should reevaluate our reliance on ESLint to do "all the things" and instead choose the best tool for the job for TS/JS formatting and other automated checks. This may be a combination of the latest version of ESLint + some plugins/packages plus Prettier for formatting, or it may include Oxlint, or maybe something different. This is an opportunity for us to take a step back and evaluate the current options and choose the best ones for us to use for the next several years.

Use Case

When a user users the linters available in this repo, they should be able to use the best ones for the job.

[benpbolton]

Core approach / references:

@wordpress/prettier-config exists
@wordpress/scripts still using eslint 8

https://make.wordpress.org/core/2022/01/05/proposal-changes-to-javascript-coding-standards-for-full-prettier-compatibility/

[kevinfodness]

A decision on this impacts the disposition of #754

[renatonascalves]

I started to explore oxlint for the NYP, and might have more feedback soon. My initial feedback is that for less complex projects, the switch is smooth. But for more complex monorepo setups, with several custom eslint-related packages, etc, it gets fuzzy since oxlint doesn't support all the rules from eslint-related plugins yet.

[renatonascalves]

Currently, for proper i18n support, if you need to check text domains in js files, one needs to use this package: https://www.npmjs.com/package/@wordpress/eslint-plugin

WPCS removed support for checking js files, so this package is the new way to do it. We should take that into account.

Currently, in the NYP project, we are using OXlint + ESlint (using this package).

The block editor project is also working on a update that will support both ESlint v8 and v9. See WordPress/gutenberg#64782 and WordPress/gutenberg#65648

Which would make our lives easier here. Essentially, we could upgrade to eslint v9, and allowing folks on v8 to continue to use it. And introduce oxlint support for those that want to.