links

Configure tRPC client link chains with terminating links and splitLink routing.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill links-plazacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: links
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/links
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill links-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers configure tRPC client link chains so operations are routed correctly, subscriptions are handled by the right transport, and terminating links prevent runtime failures.

Core Features & Use Cases

  • Terminate link chains correctly using httpLink, httpBatchLink, httpBatchStreamLink, wsLink, httpSubscriptionLink, or unstable_localLink to avoid "no more links to execute" errors.
  • Route subscription operations through splitLink to SSE or WebSocket transports and disable batching per-request via context flags.
  • Tune batching limits and streaming behavior with options like maxURLLength, maxItems, and stream headers, and compose custom links for service-oriented routing and timing/logging instrumentation.

Quick Start

Create a tRPC client that uses splitLink to send subscription operations to an EventSource-based httpSubscriptionLink and all other operations to an httpBatchLink with appropriate maxItems and headers.

Frequently Asked Questions about links

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my tRPC client throw a no more links to execute error?

A no more links to execute error occurs when your tRPC client link chain lacks a terminating link. You must end the chain with httpLink, httpBatchLink, wsLink, or httpSubscriptionLink to route operations correctly and prevent runtime failures.

How do I route tRPC subscriptions to SSE or WebSocket transports?

You route tRPC subscriptions by composing a splitLink that directs subscription operations to an EventSource-based httpSubscriptionLink or wsLink, while sending all other operations to a standard httpLink or httpBatchLink.

How do I disable tRPC batching for a specific request?

You disable tRPC batching per-request by setting context flags within your link chain, allowing individual operations to bypass the httpBatchLink and execute immediately through a standard httpLink instead.

What options can I configure on tRPC client links for streaming and batching?

You can configure tRPC client links using options like maxURLLength, maxItems, headers, transformer, and stream headers. These tune batching limits, streaming behavior, and connection parameters for httpBatchStreamLink and httpSubscriptionLink.

Can I compose custom tRPC links for service-oriented routing?

Yes, you can compose custom tRPC links using splitLink branches to achieve service-oriented routing. This allows you to direct operations to different endpoints and integrate timing or logging instrumentation within your client setup.

Does tRPC support SSE subscriptions in browsers without native EventSource?

Yes, tRPC supports SSE subscriptions in environments lacking native EventSource by allowing you to specify an EventSource ponyfill within the httpSubscriptionLink configuration to handle the connection.