2022-02-18
2010
#js libraries
Ben Holmes
93166
Feb 18, 2022 ⋅ 7 min read

Testing Vite with minimal config using Vitest

Ben Holmes I'm a web dev, UX freak, and restless tinkerer. Let me teach you the art of building websites!

Recent posts:

When is low-code the right choice? Here’s how to decide

Not sure if low-code is right for your next project? This guide breaks down when to use it, when to avoid it, and how to make the right call.

Popoola Temitope
Jul 11, 2025 ⋅ 7 min read
Comparing AI App Builders — Firebase Studio vs. Lovable vs. Replit. LogRocket Article

Comparing AI app builders — Firebase Studio vs. Lovable vs. Replit

Compare Firebase Studio, Lovable, and Replit for AI-powered app building. Find the best tool for your project needs.

Emmanuel John
Jul 11, 2025 ⋅ 7 min read
Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Discover how to use Gemini CLI, Google’s new open-source AI agent that brings Gemini directly to your terminal.

Chizaram Ken
Jul 10, 2025 ⋅ 8 min read
React & TypeScript: 10 Patterns For Writing Better Code

React & TypeScript: 10 patterns for writing better code

This article explores several proven patterns for writing safer, cleaner, and more readable code in React and TypeScript.

Peter Aideloje
Jul 10, 2025 ⋅ 11 min read
View all posts

3 Replies to "Testing Vite with minimal config using Vitest"

  1. Note: Vitest is still not recommended for production use as of February 2022. Check Vitest’s homepage for up-to-date suggestions before using it.

    I can’t find this content. please link
    Can I use it in production now?

  2. It seems like vitest have not only inherited jest’s API syntax but also the issue of not being able to mock CommonJS functions declared within the same module (https://github.com/vitest-dev/vitest/discussions/3667).
    While with jest there is a workaround to use babel-plugin-rewire without altering the testing code (https://github.com/jestjs/jest/issues/936#issuecomment-545080082), could not get it to work with vitest so far.
    And this issue is very critical for my tests.

Leave a Reply