Docs: use new defineConfig, plugins and extends

[tbroyer]

ESLint now recommends using defineConfig() and using plugins: and extends: to apply plugins and import configs. It also recommends specifying a files: (now that ESLint supports other file types)

I do have one issue though in that the key depend is apparently already used by ESLint internally so I have to use a different name; it would be good that the document suggests such a name.

import { defineConfig } from "eslint/config";
import * as moduleReplacements from "eslint-plugin-depend";

export default defineConfig([
    {
        files: ["**/*.js"],
        plugins: {
            moduleReplacements,
        },
        extends: [ "moduleReplacements/flat/recommended" ],
    }
]);

[43081j]

so they've gone back to how it was before flat config?

didn't everyone just spend the last year migrating to the new format? 😂

specifically this:

        extends: [ "moduleReplacements/flat/recommended" ],

is going backwards. they moved off this so we could pass concrete objects in as config instead of relying on some internal resolution. so now it relies on internal resolution again to figure out what this syntax refers to?

[43081j]

#42

maybe this time it'll stay this way a while 😅

[tbroyer]

they moved off this so we could pass concrete objects in as config instead of relying on some internal resolution. so now it relies on internal resolution again to figure out what this syntax refers to?

With a big difference: it won't resolve NPM modules, the plugin has to have been added in plugins:, and the prefix is the key it was registered as (so no eslint-plugin-depend/flat/recommended or depend/flat/recommended with an implied eslint-plugin- prefix)

[43081j]

that makes sense 👍

i saw you can also reference it if you already imported it, which is what i've done in the PR. let me know if that seems ok