chore: fix vitest types test setup #115
Merged
+24
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current setup Vitest does not report type errors in the type test file, so the file will always succeed. Issues would still be picked up by
tscso it isn't the worst, but my expectation would be use Vitests type testing correctly. Especially when working on some types (which I might be doing right now 😄) Vitest can give quicker feedback.I changed the setup a bit to enable this which also has the upside that you can run
pnpm test --project Xdepending on what you are currently working.