Skip to content

Bug: [new config system] globs are ignoring dot files #16265

Closed
@mdjermanovic

Description

Environment

Node version: v16.14.0
npm version: v8.3.1
Local ESLint version: v8.23.0 (Currently used)
Global ESLint version: Not found
Operating System: win32 10.0.19044

What parser are you using?

Default (Espree)

What did you do?

// eslint.config.js

module.exports = [];
// .foo.js
npx eslint *.js -f tap

What did you expect to happen?

Per the RFC, this should include .foo.js?

  1. Defaults - by default, ESLint will ignore node_modules and .git directories only. This is different from the current behavior where ESLint ignores node_modules and all files/directories beginning with a dot (.).

In that case, I would expect this output:

TAP version 13
1..2
ok 1 - D:\tmp\tmp\.foo.js
ok 2 - D:\tmp\tmp\eslint.config.js

What actually happened?

The .foo.js file was not linted:

TAP version 13
1..1
ok 1 - D:\tmp\tmp\eslint.config.js

Participation

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

Additional comments

No response

Metadata

Assignees

Labels

acceptedThere is consensus among the team that this change meets the criteria for inclusionarchived due to ageThis issue has been archived; please open a new issue for any further discussionbugESLint is working incorrectlyneeds bikesheddingMinor details about this change need to be discussedrepro:yesIssues with a reproducible example

Type

No type

Projects

  • Status

    Complete

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions