Pelle Wessman

Looks like the building of the types and the publishing failed: https://github.com/jsx-eslint/eslint-plugin-react/actions/runs/11062995632/job/30739408890 Yet it did publish 🤔

As I posted in the other issue at the very moment this issue was posted: I think this “simply” amounts to merging `main` into `v8`, as seems to have been...

> Can you explain more about what config-inspector does and what it needs? Two things: 1. When it resolves the config it needs to know the default config which ESLint...

> Yes. I'd say the best place to start is just to use `@eslint/config-array` directly. The file matching logic is all encapsulated there and you'll get the same results as...

The `flatConfigSchema` would kind of also be needed to load an ESLint flat config into `@eslint/config-array`, as else it complains of eg. `Unexpected key "languageOptions" found.` https://github.com/eslint/eslint/blob/21d3766c3f4efd981d3cc294c2c82c8014815e6e/lib/config/flat-config-schema.js#L548-L566

The config-inspector now uses `@eslint/config-array` at its core, using a minimal schema: https://github.com/eslint/config-inspector/blob/ca6070e86bd6a5aa6f11cf1d9fc9bd0d9e956e97/src/configs.ts#L212-L243

Maybe one can skip the first of the configs and only expose these? To avoid exposing rules etc https://github.com/eslint/eslint/blob/e2b16e2b72606162dce3d804bc80186b6c5ec0f9/lib/config/default-config.js#L56-L74

One could possibly do the first but name it something like `.referenceDefaultConfig`, to make it clear that its to be used as a reference, not as a config

@nzakas My thought was that there's a difference between _using_ a config and _referencing_ a config, and if one wants to avoid confusion where people start using this config in...

Sure, I can do that, I will try to get to it soon 👍