software-mansion / software-mansion/TypeGPU
chore: vitest --project=!browser might be a noop
Open
Nobody has claimed this yet.
exploration
- Dominant language
- TypeScript
- Stars
- 3.2k
- Forks
- 122
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 34
Description
We've recently got a report that vitest --project=!browser might not actually filter anything out, this might have stopped working during our migration from Vitest 3 to Vitest 4.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running vitest --project=!browser and compare its project selection with the expected behavior. Review the Vitest configuration and the recent migration from Vitest 3 to Vitest 4; done means confirming whether the browser project is excluded and identifying the configuration change needed if it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100