Flat Config: Ignores

[msalsbery]

I've been going insane trying to get this to work....seems like it should be obviously simple and common...

I've converted a couple projects to the new config. I run eslint CLI from a root folder (where eslint.config.js resides) something like npx eslint **/* or npm run lint (where the "lint" script is eslint **/*).

There's a folder off the project root called build. I don't want any js file in that folder or any of its subfolders linted.

Does anyone have an example of the simplest eslint.config.js that ignores a folder called build?

[msalsbery]

Ok, obviously this works

export default [
  js.configs.recommended,
  {
    ignores: ['build/'],
  },
];

Where it starts to fail is when I thought I was adding "global" language options

export default [
  js.configs.recommended,
  {
    ignores: ['build/'],
    languageOptions: {
      ecmaVersion: 2020,
      sourceType: 'module', // module, script, commonjs
      globals: {
        ...globals.es2020,
        ...globals.node,
        ...globals.shelljs,
      },
    },
  },
];

ignores is ignored as soon as I add languageOptions there. Since my projects have Typescript as well always, I moved the language options to a files: ['**/*.{js,mjs,cjs}'] config object and the ignores is now still working.

Clearly I don't have a firm grasp on how this flat config works yet...

[msalsbery]

Well shoot...

If ignores is used without any other keys in the configuration object, then the patterns act as global ignores

Note that only global ignores patterns can match directories. ignores patterns that are specific to a configuration will only match file names

RTFM for the 6th time and read ALL the sentences (and have a public discussion with yourself) to ensure success!

[elliot-huffman]

same, I read it through it just didn't click for me. Thank you for this post, it helped a ton!

[cmahnke]

I've been bitten by this to. It took me some time to find this post. The current way is quite suboptimal. It would be easier to decouple meaning and semantics here:

• There should be a globalIgnores which works regardless of it's suroundigs. That way it would be easier to understand (and override) what's going here. The current way is way less to expressive...