Skip to content

Comments

chore: remove vite-plus (for now)#1529

Open
wojtekmaj wants to merge 3 commits intonpmx-dev:mainfrom
wojtekmaj:no-vite-plus
Open

chore: remove vite-plus (for now)#1529
wojtekmaj wants to merge 3 commits intonpmx-dev:mainfrom
wojtekmaj:no-vite-plus

Conversation

@wojtekmaj
Copy link
Contributor

It seems like we're currently using vite-plus solely for running tests. It caused issues in the past that forced us to migrate away from it in most places (vite fmt, vite lint running postinstall and causing severe delays). It currently crashes on Windows arm64 machines. It is also explicitly said:

Vite+ is not yet stable and should not be used in production.

With that in mind, vite-plus does not provide a lot of value to the project at the moment and therefore I propose removing it for now.

It seems like we're currently using vite-plus solely for running tests. It caused issues in the past that forced us to migrate away from it in most places (vite fmt, vite lint running postinstall and causing severe delays). It currently crashes on Windows arm64 machines. It is also explicitly said:

> Vite+ is not yet stable and should not be used in production.

With that in mind, vite-plus does not provide a lot of value to the project at the moment and therefore I propose removing it for now.
Copilot AI review requested due to automatic review settings February 16, 2026 09:11
@vercel
Copy link

vercel bot commented Feb 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs.npmx.dev Ready Ready Preview, Comment Feb 24, 2026 11:57am
npmx.dev Ready Ready Preview, Comment Feb 24, 2026 11:57am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
npmx-lunaria Ignored Ignored Feb 24, 2026 11:57am

Request Review

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the experimental vite-plus package that was causing compatibility issues on Windows arm64 machines. The package was only being used for testing and is explicitly marked as unstable. The migration replaces vite-plus with the standard stable versions of vite and vitest.

Changes:

  • Removed vite-plus package overrides from pnpm workspace configuration
  • Updated all test scripts from vite test to vitest
  • Removed vite-plus dependency entries from package.json and knip configuration

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File Description
pnpm-workspace.yaml Removed vite and vitest overrides that aliased to vite-plus packages
pnpm-lock.yaml Updated dependency tree to use standard vite/vitest instead of vite-plus variants
package.json Updated test scripts to use vitest command and removed vite-plus dependencies
knip.ts Removed vite-plus from ignored dependencies list
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e58a0d5 and 68c36e1.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json

📝 Walkthrough

Walkthrough

Removed two packages from knip.ts ignoreDependencies: '@voidzero-dev/vite-plus-core' and 'vite-plus'. package.json updated: test scripts now run vitest with project flags, vite-plus removed from dependencies, and vitest pinned to ^4.0.18. pnpm-workspace.yaml had two overrides removed (for vite and vitest referencing @voidzero-dev pre-release packages). No exported/public signatures were changed.

Possibly related PRs

Suggested reviewers

  • danielroe
  • firstangler59
🚥 Pre-merge checks | ✅ 1
✅ Passed checks (1 passed)
Check name Status Explanation
Description check ✅ Passed The pull request description clearly explains the rationale for removing vite-plus, detailing specific issues encountered and referencing stability concerns.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@43081j
Copy link
Contributor

43081j commented Feb 24, 2026

caught up the branch for you.

i agree we should use vitest until the void zero branch is stable enough.

@danielroe
Copy link
Member

if we can itemise issues we can pester @TheAlexLichter to fix them 👀

@TheAlexLichter
Copy link
Contributor

In all cases, please send issues! This is super valuable for the upcoming alpha and to improve Vite+ further.

@danielroe
Copy link
Member

I think voidzero-dev/vite-plus-discussions#9 is the most pesky one right now.

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.

4 participants