We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Eg. support for the Request and Response objects specified in the Fetch Standard. It would allow deploying to Remix routes for example.
Unfortunately I don't have the time to work an a proper PR but I created a userland adapter that can be used with Remix:
https://github.com/valu-digital/npm-packages/tree/master/packages/trpc-fetch-api-adapter
The implementation is probably very naive but at least it is some short of starting point.
The text was updated successfully, but these errors were encountered:
Yes, I actually started this refactoring once, should be picked up for sure!
Sorry, something went wrong.
forgot to close this, added in the next branch - #1852
next
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.
Successfully merging a pull request may close this issue.
Eg. support for the Request and Response objects specified in the Fetch Standard. It would allow deploying to Remix routes for example.
Unfortunately I don't have the time to work an a proper PR but I created a userland adapter that can be used with Remix:
https://github.com/valu-digital/npm-packages/tree/master/packages/trpc-fetch-api-adapter
The implementation is probably very naive but at least it is some short of starting point.
The text was updated successfully, but these errors were encountered: