-
Notifications
You must be signed in to change notification settings - Fork 4
Test older Vite versions #864
Copy link
Copy link
Open
Labels
@arkenv/vite-pluginIssues or Pull Requests involving the Vite plugin for ArkEnvIssues or Pull Requests involving the Vite plugin for ArkEnvtestsThis issue or PR is about adding, removing or changing testsThis issue or PR is about adding, removing or changing tests
Metadata
Metadata
Assignees
Labels
@arkenv/vite-pluginIssues or Pull Requests involving the Vite plugin for ArkEnvIssues or Pull Requests involving the Vite plugin for ArkEnvtestsThis issue or PR is about adding, removing or changing testsThis issue or PR is about adding, removing or changing tests
Right now we have a "vite-legacy" playground to softly back up the peer dependency range declared in
@arkenv/vite-plugin:Current state
vite-legacyis pinned to Vite 7 — it builds as part ofpnpm run buildvia Turbo, so CI does verify at least one non-latest major.peerDependenciesis untested and unverified.Long-term plan
Add a CI matrix job (in
test.yml) that installs and buildsvite-legacyagainst each claimed major:Each job would override the
vitedep (e.g. viapnpm --override vite@${{ matrix.vite-version }}) and runpnpm run build --filter=vite-legacy-playground.Until that matrix exists, the
peerDependenciesfloor should stay at^7.0.0(the lowest actually tested version) to avoid false promises to users on older Vite versions. Once the matrix is in place, the floor can be lowered only as far as the matrix validates.