ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #turbo
Learn how to eliminate full-page reloads in Ruby on Rails using Turbo Frames to create a snappier, SPA-like experience without leaving the server-side ecosystem.
Learn how to implement Remote Caching in Turborepo to eliminate redundant builds across CI/CD pipelines and distributed development teams.
Learn when to pick Turbo Frames or Turbo Streams for partial page updates, see a concise comparison table, and view concrete Rails‑style implementation snippets.
Learn how to use Turbo Frames to isolate page updates and eliminate full-page reloads in server-side rendered applications, maintaining a fluid user experience without complex JS.
Turbo Frames support deferred loading through the loading='lazy' attribute on turbo_frame_tag in Rails 7.1 and later. The objective is to lower initial-page bandwidth and server requests for a low-traffic workload by fetching offscreen frame content only when it enters the viewport. Each lazy frame currently issues an independent HTTP GET to its src URL on s
Turborepo 2.x introduced changes to internal cache boundaries and task graph execution compared to 1.x. The goal is to understand remote caching and task hashing behavior after this configuration transition while testing an integration without production credentials. Credential-less testing is constrained to local file cache fallback because Vercel Remote Ca
Turbo Frames are documented to follow HTTP redirects automatically when fetching a frame's source, replacing the frame content with the redirect target rather than triggering a full page navigation. In practice, browser implementations of fetch and XMLHttpRequest redirect handling may diverge from this documented behavior, particularly when a server returns
The goal is to determine why navigation from a link inside a Turbo Frame results in a full document visit instead of a partial frame replacement. Turbo Drive intercepts the click and expects the server HTML to include a <turbo-frame> element whose id matches the originating frame. If that element is absent or mismatched, Turbo discards the partial resp
Turbo Drive's documented fallback mechanism converts failed Ajax visits into full page loads, but the exact boundary between recoverable and unrecoverable failures remains unclear when requests neither succeed nor explicitly reject. The handbook describes fallback for non-2xx responses and aborted requests, yet the behavior for requests that hang without a r
rails