You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running vp exec void init on a Vite+ migrated repo I get the following error:
import { parseSync } from "vite";
^^^^^^^^^
SyntaxError: The requested module 'vite' does not provide an export named 'parseSync'
at #asyncInstantiate (node:internal/modules/esm/module_job:319:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:422:5)
at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:661:26)
*Note on a window
According to codex:
The issue is not with your PAT or .npmrc. It’s a dependency conflict.
void init expects the real vite package and imports parseSync from it, but in this repo vite is overridden to Vite+ core in package.json, and the installed vite package is actually node_modules/vite/package.json, which is @voidzero-dev/vite-plus-core. That package does not export parseSync, so vp exec void init crashes immediately.
The failing error is:
SyntaxError: The requested module 'vite' does not provide
Activity
TheAlexLichter commentedon Jun 7, 2026
Fixed at least in the latest Vite+ (can't repro anymore).
fix: force database binding when migrations exist (bump framework) (#72)