feat: Remove that unstable imports that we can from the libs
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 40.6k
- Forks
- 1.7k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 22
Description
Describe the feature you'd like to request
We use a bunch of imports from @trpc/server/unstable-core-do-not-import.
Describe the solution you'd like to see
We should prefer using @trpc/server whenever we can
-
@trpc/next- #5485 -
@trpc/react-query -
@trpc/client
Describe alternate solutions
Create a @trpc/server/plugin entrypoint or something that can export explicit stuff for plugins
Additional information
No response
👨👧👦 Contributing
- 🙋♂️ Yes, I'd be down to file a PR implementing this feature!
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 searching the @trpc/next, @trpc/react-query, and @trpc/client packages for imports from @trpc/server/unstable-core-do-not-import, beginning with the @trpc/next work tracked in #5485. Compare each import with the public @trpc/server entrypoint and run the affected package tests; done means unstable imports are removed wherever the public entrypoint provides the required API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- api, backend-api-design, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100