Skip to content

Bug: [new config system] Unexpected glob behavior in FlatESLint #16340

@fisker

Description

@fisker

Environment

Node version: 18.8.0
npm version: N/A
Local ESLint version: 8.23.1
Global ESLint version: A/A
Operating System: Windows

What parser are you using?

Default (Espree)

What did you do?

Run FlatESLint with different cwd on same file.

What did you expect to happen?

Should result the same.

What actually happened?

They result differently.

Participation

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

Additional comments

Step to reproduce:

  1. Clone the repo https://github.com/fisker/flat-eslint-cmd-bug-repo (or run on gitpod.io)
  2. run yarn && node test.mjs to see the difference

It seems the globby option {absolute: true} cause globby can't match any file.

Remove that line cann't really fix my problem, but it should be another issue, possible related to #16264

Since the globby version we are using is really old, not sure what causes that. (I'm a maintainer of globby)

Metadata

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 incorrectlycoreRelates to ESLint's core APIs and featuresrepro: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