Repository navigation
fix(deploy): keep framework Worker Wasm imports as Wasm modules - #536
Closed
Pleasurecruise wants to merge 1 commit into
Closed
Pleasurecruise wants to merge 1 commit into
Pleasurecruise wants to merge 1 commit into
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
1 participant
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.
prepareBundledBuildOutputnow keeps.wasmimports external and emits each file beside the bundle, socopyBundleuploads it with thewasmmodule type instead of Vite bundling it as ES module integration.Test
cf-build-output.test.ts: static and dynamic.wasmimports (including a wasm-bindgen-stylewbgimport and the same file from two modules) become twowasmmodules and passcfdry-run. Fails without the fix.vp test run packages/void/test/unit/cf-build-output.test.tsandvp run --filter ./packages/void typecheckpass.@resvg/resvg-wasm.