Why use 'forks' instead of 'threads' in Node 22+?

Threads have known native fetch issues in Node 22+; using the 'forks' pool provides a more stable execution environment for modern Node versions.

When should I use vi.spyOn over vi.mock?

This skill recommends vi.spyOn for explicit mocking that avoids hoisting issues and allows for more predictable behavior with imported modules.

How does this skill improve CI performance?

It provides optimized patterns for single-worker execution and disabling isolation where safe to significantly reduce overhead in CI environments.

Why is defining coverage.include emphasized?

Default Vitest coverage settings often exclude critical source files; this skill ensures your coverage reports accurately reflect your entire codebase.

Does this skill help with React Testing Library?

Yes, it includes specific configuration requirements for RTL cleanup and global variable management necessary for seamless React testing.

Vitest Expert

Name: Vitest Expert
Author: phrazzld

byphrazzld

•

Seguridad y Pruebas

Optimizes Vitest configurations and testing workflows for high-performance Node.js environments.

This skill provides deep domain expertise for Vitest, focusing on performance tuning for CI/CD environments, modern Node.js compatibility (v22+), and robust mocking strategies. It helps developers audit existing vitest.config.ts files, troubleshoot complex mocking issues, and ensure accurate code coverage reporting, making it an essential companion for maintaining high-quality JavaScript and TypeScript test suites while avoiding common pitfalls like thread-related fetch issues and hoisting errors.

Características Principales

01Automated Vitest configuration auditing and optimization

02Node.js 22+ compatibility fixes and pool selection optimization

03Comprehensive coverage reporting setup and threshold configuration

04Expert guidance on mocking strategies and vi.spyOn implementation

055 GitHub stars

06Performance tuning for CI/CD environments and parallel execution

Casos de Uso

01Migrating test suites to Node.js 22 or higher using the forks pool

02Troubleshooting flaky tests caused by mocking hoist issues or state leakage

03Reducing CI test execution time through worker and isolation optimization

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add phrazzld/claude-config vitest

For use in Claude.ai and ChatGPT

Download Skill