New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decouple @trpc/server
from node
#1597
Labels
💸 Get paid!
I'll send you money through your GitHub sponsors for addressing this
⏭ major bump needed
Requires a major version bump
Comments
KATT
added
✨ enhancement
⏭ major bump needed
Requires a major version bump
💸 Get paid!
I'll send you money through your GitHub sponsors for addressing this
labels
Mar 6, 2022
Excited about this! Thanks for taking ownership, @sachinraja! |
This was referenced Apr 3, 2022
Merged
This was
linked to
pull requests
May 13, 2022
Merged
Closing this as we've now been able to deploy on CF Workers and Deno |
This issue has been locked because it had no new activity for 14 days. If you are running into a similar issue, please create a new issue. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
💸 Get paid!
I'll send you money through your GitHub sponsors for addressing this
⏭ major bump needed
Requires a major version bump
Related to the
next
branch.Currently,
@trpc/server
is using a lot of Node-based dependencies, i.e.url
,http
, etc.It would be great to decouple
@trpc/server
completely from a node in order to easier deploy tRPC to i.e. CF workers (#1375).Proposal
Rough steps:
@trpc/server
to@trpc/node
(and update all examples, etc)@trpc/core
@trpc/core
or similarresolveHTTPResponse
should still exist as part of@trpc/core
but with a slightly different signature.@trpc/node
could have a hard dependency (rather than a peerDep) of@trpc/core
andexport * from '@trpc/core'
./examples
foldernext
-branchPayment
I'll pay $200 if someone addresses it. If you think that isn't enough, feel free to contact me. Payment will be through GitHub sponsors - see #1599.
The text was updated successfully, but these errors were encountered: