ESLint version

v8, v9

What problem do you want to solve?

Right now, we use the /use-at-your-own-risk entrypoint for accessing non-default objects like FlatESLint and LegacyESLint, but doing so requires integrators to pull from different locations depending on which mode they want to run ESLint in. This is error-prone, especially if they don't know the version of ESLint ahead of time.

What do you think is the correct solution?

Add an API, exported from the main entrypoint, that allows access to the correct APIs and provide that in v8, v9, and v10 to ease integration difficulty.

Potentially move shouldUseFlatConfig to the main entrypoint as an export.

Participation

• I am willing to submit a pull request for this change.

Additional comments

No response