refactor(demo): use h3/nitro for deployment packaging #146
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
h3.toNodeListener
curl -d '{}' https://vite-plugins-demo-hiro18181-m2qcwe9g9-hiogawa.vercel.app/trpc/me
dist/client/assets
blocker?
Actually there are too much indirection between web req/res and node req/res due to:
Request.body
ahead of time...https://github.com/unjs/nitro/blob/c40a3bd0cb13799ce00d66173eb8107277d6e5e5/src/runtime/entries/cloudflare-module.ts#L49
https://github.com/unjs/nitro/blob/c40a3bd0cb13799ce00d66173eb8107277d6e5e5/src/runtime/entries/vercel-edge.ts#L9
toWebRequest
will make it back to ReadableStream...https://github.com/unjs/h3/blob/53703dc860f1ff6fe7ce71d543deff1cfa810b11/src/utils/request.ts#L181-L192
toNodeListener
internally...https://github.com/unjs/nitro/blob/c40a3bd0cb13799ce00d66173eb8107277d6e5e5/src/runtime/app.ts#L95-L105
The movement to reduce indirection on h3 seems to be finished in:
But maybe nitro integration still has some issue?