Repository navigation
fix(core): resolve bundled dev runtime from core - #3111
Merged
Merged
Conversation
cpojer
approved these changes
Oct 19, 2026
fengmk2
force-pushed
the
fix/bundled-dev-runtime
branch
from
October 19, 2026 06:08
a5f1a16 to
9a3c8e7
Compare
fengmk2
added
test: e2e
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vp devfails withERR_MODULE_NOT_FOUNDwhenexperimental.bundledDevistrueand no separaterolldownpackage exists. An installedrolldownpackage can also supply the wrong runtime.The core build now resolves the runtime through
@voidzero-dev/vite-plus-core/rolldown/experimental/runtime. It keepsROLLDOWN_DEV_RUNTIME_ENTRYunchanged so Vite can rewrite the browser client import. The WebContainer fallback also uses the bundled Rolldown version directly, without arolldown/package.jsonlookup.An artifact snapshot records remaining bare Rolldown package names and their uses across built JavaScript and declarations. New references require review, including package lookups through constants or aliases. A packed-package snapshot checks fresh and cached WASM fallback paths in a simulated WebContainer without a separate
rolldownpackage.Set the
vibe-dashboardecosystem revision tobe10551d4b73b7bcb53491311b574fb214a38e1ffrom voidzero-dev/vibe-dashboard#370. That revision enablesexperimental.bundledDevoutside Vitest runs because Vitest does not support this mode. The ecosystem job runs the project'svp run test:devcommand to check rendering, lazy routes, and reloads in Chromium.Fixes #3110.