Why I Avoid Working With WebSockets in NextJS and tRPC
From the video description
When working on a new WebSockets project in tRPC and NextJS I realized some limitations that could (maybe?) be bypassed somehow, however online resources on this specific topic are scarce. Personally, I much prefer a traditional express / WebSockets in nextjs approach, leaving type safety out of the equation. Thanks for watching, if you have a similar or completely different experience I'd be happy to hear your thoughts! :^)
Topics
Sources
Video by Josh tried coding, played through YouTube.
- Indie Picks
Data and selection notes
Indie Picks uses video metadata for classification. The description above is an uploader excerpt, not an independent review.
Indie Picks: Independently collected SaaS and AI product videos, organized by a founder handbook. Topics and relevance are metadata-indexed; full-video editorial review has not been completed. Descriptions are uploader excerpts where available.
Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.
Selection checks
- SaaS & AI candidates: Matches the configured criteria
- Editor-approved picks: Editorial review is required