Draft
Conversation
7 tasks
This reverts commit f52fc38.
github-merge-queue bot
pushed a commit
to rolldown/rolldown
that referenced
this pull request
Feb 6, 2025
<!-- Thank you for contributing! --> ### Description Follow up to #3488. I forgot to test `emitFile({ type: "chunk" })` case and I just realized it's not working on hi-ogawa/vite-environment-examples#154. Currently, `FileEmitter::emitted_chunks` is not defined during scope hoisting finalizer, but it looks possible to define it earlier right after `generate_chunk_name_and_preliminary_filenames` instead of waiting until `instantiate_chunks`.
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.
todo
examples/react-server
https://github.com/vitejs/vite-ecosystem-ci/blob/rolldown-vite/README-temp.md#vite-environment-examples
parseAstAsyncrollup/parseAstvirtual:copy-server-css.jsthe issue is that 2nd rsc build's manifest includes css output which is only available in 1st rsc build.not only css, but also__client-CCH4vHkY.jschunk is included in manifest.it looks like only manifest issue and two builds are mostly working fine.but the difference is that rolldown now generates_client.js(and thus_client.css) in 1st rsc build, which wasn't the case. Maybe I was relying on no side effect elision, which is not working on rolldown?but the difference is that previously there are less chunks in rollup and thus manifest entry is overwritten without stale content showing up after 2nd rsc build
though we might need to revisit double environment build to avoid this type of issue
examples/web-worker
import.meta.ROLLUP_FILE_URL_xxximport.meta.ROLLUP_FILE_URL_(referenceId)rolldown/rolldown#3488emitFile({ type: "chunk" }