Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Picomatch: Expected pattern to be a non-empty string #462

Open
2 tasks done
felixranesberger opened this issue Feb 25, 2025 · 2 comments
Open
2 tasks done

Picomatch: Expected pattern to be a non-empty string #462

felixranesberger opened this issue Feb 25, 2025 · 2 comments

Comments

@felixranesberger
Copy link

Describe the bug

After updating to v0.9.0 I get the following error:

Image

Reproduction

Config:

 checker({
        root: process.cwd(),
        overlay: {
          initialIsOpen: false,
        },
        // activate typescript type checking only if the entry file is a typescript file
        typescript: configurationBase.entry.endsWith('.ts'),
        eslint: {
          lintCommand: `eslint -c ./${configurationBase.eslint} .`,
          useFlatConfig: true,
        },
        stylelint: {
          lintCommand: `stylelint -c ./${configurationBase.stylelint} ${resolvePath(configurationBase.entryDir)}/**/*.{css,scss,sass,less}`,
        },
      }),

Expected behavior

.

System Info

.

Additional context

No response

Validations

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
@tryforceful
Copy link

tryforceful commented Feb 27, 2025

I also get this error. It seems to be generated from the eslint configuration, specifically when I specify . as the source files location...

E.g. this causes the error and crash:

eslint: {
    lintCommand: 'eslint .',
    useFlatConfig: true,
  },

But this is OK (linting only in a sub directory):

eslint: {
    lintCommand: 'eslint src',
    useFlatConfig: true,
  },

EDIT

It seems specifying **/* instead of . could be a temporary solution?

@thomasoehri
Copy link

I'm also getting this error and @tryforceful's workaround seems to work for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants