ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #vitest
Learn how to diagnose and fix 'Timeout' errors in Vitest. This guide covers identifying CI vs. local failures, auditing async patterns, and applying targeted configuration fixes.
Learn how Vitest leverages Vite’s dev server and hot module replacement to give you near‑instant test feedback, with a concrete setup example, trade‑offs, and CI usage.
Vitest projects let one root config run node and jsdom test suites together in a monorepo. A worked two-package example, filtering for fast local loops, and the memory and coverage trade-offs.
Learn how to use Vitest Workspaces to manage multi-package monorepos, enabling isolated environments like jsdom and node while sharing a single worker pool for performance.
When running Vitest tests that reside in nested directories, the framework automatically creates a .vitest/__snapshots__ folder. The default expectation is that this folder appears adjacent to the test file, but in some project layouts the snapshot files end up under the Vite root instead. The Vite configuration exposes a snapshotResolver option, yet the doc
Integration boundary Vitest hoists vi.mock calls before imports execute, while Vite's plugin pipeline resolves virtual modules (e.g., .vue , @vitejs/plugin-vue generated entries) during resolveId and load hooks. The documentation states mocks are "fully hoisted" but does not specify whether hoisting occurs before or after Vite's resolve hooks, leaving plugin
Problem Overview Vitest uses the Node.js Date implementation, which follows the process.env.TZ setting. When tests involve date‑manipulation libraries such as date‑fns‑tz , the output can vary between a developer’s machine and CI runners that have different default time zones. Current Constraints Vitest provides no built‑in helper to override or mock the sys
Goal Gradually shift a small application’s test suite from Jest to Vitest while keeping local development and CI pipelines operational. Constraints Vitest runs in a separate Node environment and hoists vi.mock calls statically above all imports, unlike Jest’s transform‑based timing. Path aliases and browser globals must be re‑declared, and in‑memory fixtures
Accessibility of Vitest's Browser Test Runner UI Vitest provides a browser-based test runner with an interactive UI panel for test discovery and execution. This interface allows developers to filter, run, and inspect test results visually. However, the accessibility of this UI—particularly for users who rely on keyboard navigation—is not explicitly documente
vite
nodejs
jest