feat: support wasm module asset #548
Closed
Conversation
This file contains 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
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
hi-ogawa
changed the title
hi-ogawa
changed the title
9 tasks
hi-ogawa
force-pushed
the
feat-cf-wasm-asset
branch
from
acb1185
to
150cba1
Compare
10 tasks
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.
@vercel/og(server wasm asset + font asset) (edge) #547This already doesn't looks so trivial and I'm not sure if sveltekit (or any Vite framework) actually supports this pattern for both dev and build.
Clearly this is harder than basic binary assets, so maybe we should try that first:
Also I'm not sure how Next.js is actually deploying edge assets, so we need to research that first.