chore: fix vitest types test setup#115
Conversation
🚨 Preview Deployment Blocked - Security ProtectionYour pull request was blocked from triggering preview deployments Why was this blocked?
How to resolve this:Option 1: Get Collaborator Access (Recommended) Option 2: Request Permission Override For Repository Administrators:To disable this security check ( This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments. 🛡️ Learn more about this security featureThis protection prevents unauthorized users from:
Preview deployments are powerful but require trust. Only users with repository write access can trigger them. |
Norbiros
left a comment
There was a problem hiding this comment.
LGTM! BTW, thanks for contributing a lot to this project ❤️
My pleasure and thank you for stepping in as maintainer and keeping the project alive! |
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.