Repository navigation
Conversation
Member
Author
How to use the Graphite Merge QueueAdd the label graphite: merge-when-ready to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
✅ Deploy Preview for rolldown-rs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://revert-revert-lazy-one-request-rolldown-rs.voidzero-docs.workers.dev (commit 71b6415)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
This was referenced Sep 28, 2026
h-a-n-a
force-pushed
the
revert-revert-lazy-one-request
branch
from
October 16, 2026 15:15
38ce903 to
71b6415
Compare
This branch has not been deployed
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
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.

Relands #10789, which #10982 reverted.
#10982 was a temporary revert for vitejs/vite#23547. The Vite fix, vitejs/vite#23568, has now landed: Vite serves the dev runtime from the installed rolldown, instead of a copy built into Vite.
Differences from #10789
__rolldown_runtime__.requestLazy(realStableId, proxyId). The runtime builds the/@vite/lazyrequest inDevRuntime#loadLazyChunk. A dev server that serves the endpoint at another URL overrides that method (Vite uses it to add itsbase, bundledDev + non-root base: dynamic import requests /@vite/lazy without base → 404 vitejs/vite#23216).requestLazyskips the server only when the module and every static import it reaches already ran or have a factory in the tab (isRunnableHere). A registered factory alone is not enough: a patch can ship a module without its deps (fix(dev/lazy): ship the deps of a module that a patch shipped but never ran #11028).Release note: pair with the next Vite release
This change needs a Vite version that includes vitejs/vite#23568. With older Vite,
experimental.bundledDevbreaks on every dynamic import:Why older Vite breaks:
requestLazy.~range (~1.2.9in 8.3.1,~1.2.6in 8.3.0). A~range accepts new patch versions.To avoid that, this should ship in a minor release (1.3.0), which
~1.2.xranges do not pick up. Then the next Vite can move to~1.3.0together with vitejs/vite#23568.