remote functions-like behaviour for client-only use cases
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
I love the way remote functions are set up - especially the refreshing part that "just works".
I am in a case where i'm using the Octokit SDK for my app, and it would be lovely to map together the command & query requests that i am using with the setup for remote functions. However, the issue is that it would be an unnecessary trip to send a request from client -> server, and then forward the request from server -> github, since i can just do client -> github with the SDK.
Describe the proposed solution
Is there a way to get the DX of remote functions with query & commands, but keep it client-side? Could we get something like get-user.client.ts?
Alternatives considered
Leave it up to userland
Importance
nice to have
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing remote functions behavior, especially how its query and command requests are refreshed. Define how a client-only equivalent such as get-user.client.ts would preserve that developer experience while calling the SDK directly, and verify that no client-to-server forwarding is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100