vitest.workspace.ts references sub-config files that don't exist
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 769
- Forks
- 64
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
TanStack Pacer version
main as on Apr 19 2025, 05b7c4d905fc601afb77353a3df6533d734cd896
Framework/Library version
NA
Describe the bug and the steps to reproduce it
I was browsing through https://github.com/TanStack/pacer/blob/05b7c4d905fc601afb77353a3df6533d734cd896/vitest.workspace.js, and I noticed that it references a mix of .../vite.config.ts and .../vitest.config.ts files, but when I actually explore the packages, they all only seem to have vitest.config.ts files. So the .../vite.config.ts instances should probably be changed.
I'm also surprised this is passing CI. You may want to update your testing flow so that this sort of configuration problem actually results in an error so you catch similar problems in the future.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
NA
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
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 with vitest.workspace.ts and inspect each referenced package configuration path, comparing the vite.config.ts entries with the existing vitest.config.ts files. Update the incorrect references and verify the workspace configuration and CI testing flow fail or pass appropriately when a referenced configuration is missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100