Regression: v2.1.0 makes folder globbing impossible in `vitest.workspace.ts` (No loader is configured for ".gitignore" files: .gitignore)

[kahagerman]

Describe the bug

I am aware that v2.1.0 made backwards incompatible changes, and that this was intentional.

It appears to be impossible (since v2.1.0) to glob for folders instead of files in vitest.workspace.ts.

The documentation states that this is valid configuration:

export default [
  'packages/*'
]

This appears to be incorrect, as it will now match any files in packages/ as a config file (i.e. packages/.gitignore, etc.)

I believe that this should be updated to read:

export default [
  'packages/*/'
]

Unfortunately this also does not work; it is additionally matching other files within the sub-folder as configuration files. (i.e.packages/package-1/.gitignore)

Reproduction

Previously (before v2.1.0), my vitest.workspace.ts contained:

export default ["./*"];

So all direct sub-folders (one level down) were considered packages in the workspace.

Today (when upgrading to ^2.1.0)

This works:

export default ["*/*vitest*"];

But the following all break (with some variant of No loader is configured for ".gitignore" files: .gitignore):

• original, broken as expected by v2.1.0

  export default ["./*"];

• Same but ending with /. I think we should expect this to only match folders, not files in those folders?

  export default ["./*/"];

• Excluding ./ but ending with /. I think we should expect this to only match folders, not files in those folders?

  export default ["*/"];

System Info

`vitest ^2.1.0`

Tested with vitest `2.1.1`.

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

The glob you mentioned is correct since it only matches the first level assuming you only have folders there:

Vitest will consider every folder in packages as a separate project even if it doesn't have a config file inside

[github-actions]

Hello @kahagerman. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[kahagerman]

The glob you mentioned is correct since it only matches the first level assuming you only have folders there:

Vitest will consider every folder in packages as a separate project even if it doesn't have a config file inside

This is not actually the issue I am reporting, though it is related.

Typically when globbing, a trailing / indicates to only match folders, not files.

This is not being respected (seems like every file under this path is matched), so there is no way to match only folders, and thus no way to restore the old behaviour.

[treardon17]

I'm having a similar problem but the issue is with .DS_Store files:

No loader is configured for ".DS_Store" files: .DS_Store

My vitest workspace is configured as:

import { defineWorkspace } from 'vitest/config';

export default defineWorkspace([
  'packages/*',
]);

This configuration works in 2.0.5, but breaks in 2.1.0 and 2.1.1. I'm running macOS 15. This is notably absent when running the same command in a github workflow, presumably because .DS_Store files are macOS specific.

[kahagerman]

@treardon17 Note that there was a breaking change made for workspaces in v2.1.0, check the release notes.

[sheremet-va]

This is not actually the issue I am reporting, though it is related.

Typically when globbing, a trailing / indicates to only match folders, not files.

This is not being respected (seems like every file under this path is matched), so there is no way to match only folders, and thus no way to restore the old behaviour.

This is just not true. The glob that matches only folders works correctly with / and without / at the end: https://stackblitz.com/edit/vitest-dev-vitest-9cztj4?file=vitest.workspace.ts&initialPath=__vitest__/

The glob ./* will match all the files and folders in the working directory.

Typically when globbing, a trailing / indicates to only match folders, not files.

The tinyglobby package also matches files; this might be an upstream issue.

[kahagerman]

This is not actually the issue I am reporting, though it is related.
Typically when globbing, a trailing / indicates to only match folders, not files.
This is not being respected (seems like every file under this path is matched), so there is no way to match only folders, and thus no way to restore the old behaviour.

This is just not true. The glob that matches only folders works correctly with / and without / at the end: stackblitz.com/edit/vitest-dev-vitest-9cztj4?file=vitest.workspace.ts&initialPath=vitest/

This fails if a plain file exists in packages/.

Here the only thing I changed was to add an empty packages/.gitignore file (updated stackblitz):

[sheremet-va]

And it fails correctly because the file matches your glob. If Vitest sees a file, it assumes that it’s a Vitest config. This is mentioned in the documentation.

[kahagerman]

No, packages/*/ should not match packages/.gitignore

[sheremet-va]

No, packages/*/ should not match packages/.gitignore

As I said before:

The tinyglobby package also matches files <when glob ends with "/">; this might be an upstream issue.

But there is no issue with a glob mentioned in the documentation when it is used correctly.

[kahagerman]

Ok, I see what you're saying now; I misunderstood your original comment.

I wonder if it's worth using a more mature glob library if tinyglobby doesn't support this today.