Skip to content

feat!: remove support for Vite 5 - #8202

Merged
sheremet-va merged 1 commit into
vitest-dev:mainfrom
sheremet-va:chore/remove-v5-support
Jun 21, 2025
Merged

sheremet-va merged 1 commit into
vitest-dev:mainfrom
sheremet-va:chore/remove-v5-support

Conversation

@sheremet-va

Copy link
Copy Markdown
Member

Description

Vitest 4 will use the Module Runner instead of vite-node, so we need at least Vite 6. I am not touching vite-node's dependencies here for now, as it will be moved into a separate project before Vitest 4 is released.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

@netlify

netlify Bot commented Jun 21, 2025

Copy link
Copy Markdown

✅ Deploy Preview for vitest-dev ready!

Name Link
🔨 Latest commit 5d3642c
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6856e3002095c900082a6544
😎 Deploy Preview https://deploy-preview-8202--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant