[Bug]: Ignore files in `node_modules` (which the Stylelint CLI does by default)

[gluxon]

How did you encounter this bug?

Style files in a node_modules folder are linted by the VS Code extension. They are ignored by the Stylelint CLI.

Link to Minimal Reproducible Example

https://github.com/gluxon/stylelint-node-modules-ignore-test

Code Snippet

No response

Stylelint Configuration

export default {
  rules: {
    "block-no-empty": true
  }
};

Extension Configuration

No configurations required to reproduce this.

Actual Behaviour

VS Code shows lint errors for files in node_modules.

Expected Behaviour

VS Code should ignore node_modules unless the Stylelint config un-ignores them.

Logs

No response

Stylelint Version

16.21.1

vscode-stylelint Version

1.5.3

Node.js Version

v24.4.0

Operating System

macOS 15.5

Windows Subsystem for Linux

No response

Code of Conduct

• I agree to follow vscode-stylelint's Code of Conduct

[gluxon]

I noticed that vscode-stylelint uses codeFilename when calling stylelint.lint(), which is probably why the VS Code extension and the CLI have different behavior here.

See the test at https://github.com/gluxon/stylelint-node-modules-ignore-test.

Should this be fixed in stylelint? I think the fix would entail ignoring files if codeFilename corresponds to something in node_modules. At the moment the default **/node_modules/** ignore is only applied to the files argument by stylelint.

[gluxon]

This issue popped up when a few my teammates opened a variables file in node_modules to reference available values to choose from. Since linting was enabled on this file, auto-fixers ran and mutated the file with unexpected changes.

We're currently working around this by explicitly adding node_modules to ignoreFiles. Example:

/** @type {import('stylelint').Config} */
export default {
  ignoreFiles: ["/**/node_modules/**"],
  rules: {
    "block-no-empty": true
  }
};