Repository navigation
fix(deploy): resolve hosted framework bundles with Worker conditions - #592
Merged
cpojer merged 1 commit intoOct 26, 2026
Merged
Conversation
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.
Fixes #422
bundleEntrybundles the SvelteKit Worker again for--platform voidwith a plain Vite lib build. That build used Vite's default client conditions, so dependencies resolved to theirbrowserexports:@sentry/sveltekitfailed to build, andpostgresbuilt but picked its Node build.#540 fixed the same problem for
--platform cloudflareinprepareBundledBuildOutput.bundleEntrynow uses the same conditions:WORKER_CONDITIONSplusproduction.productionis fixed rather than taken fromNODE_ENV, because a deploy bundle is always a production build.The module rules part of #540 (
.wasm,.txt,.bin, …) is not covered here (see #535).