Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of httpuv and Vitest — release velocity, themes, recent moves, and the top alternatives to consider.
httpuv ships almost nothing, which is what you want from the web server under Shiny
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
rc.2 carries one feature — a custom title for the GitHub Actions summary — and otherwise fixes the failure modes the RC period surfaced. The browser mode gets most of it: failing instead of hanging when the browser stops responding, exiting cleanly on disconnect during cancellation, and triggering Chromium GC when disk runs low. Snapshot evaluation moved server-side to work under a no-unsafe-eval CSP, and the UI now requires auth for coverage reports and every subtree request.
httpuv is the C++ HTTP and WebSocket server that Shiny runs on. Across this window it added exactly one user-facing function - runStaticServer() for serving a directory - and spent every other release on race conditions, compiler and linker changes, CRAN check warnings, and mime type table updates.
There is no direction here in the usual sense, and that is the honest read: the package is a stable foundation whose releases are triggered by the toolchain moving, by R-devel warnings, or by a threading bug surfacing under load. The one recurring theme with substance is connection reliability - WebSocket keepalive pings, race conditions in the I/O thread - which is what actually breaks Shiny apps in production.
Expect continued small releases tracking Rtools, R-devel and mime data, with any substantive change most likely coming from a threading or WebSocket issue reported by Shiny users rather than from planned work.
rc.2 carries one feature — a custom title for the GitHub Actions summary — and otherwise fixes the failure modes the RC period surfaced. The browser mode gets most of it: failing instead of hanging when the browser stops responding, exiting cleanly on disconnect during cancellation, and triggering Chromium GC when disk runs low. Snapshot evaluation moved server-side to work under a no-unsafe-eval CSP, and the UI now requires auth for coverage reports and every subtree request.
The v5 line has spent four betas and two candidates reshaping config resolution, projects, mocking defaults, and the benchmark API; this candidate adds nothing to that surface and only stabilizes it. The concentration of browser-mode and pool fixes says that is where the remaining risk sits, and where real-world RC adoption is finding edges.
On this trajectory the next tag is either a final 5.0.0 or one more candidate, with browser mode the deciding factor rather than any remaining API work.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either httpuv or Vitest.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity ships across every package at once, and the agent-facing surface moves fastest.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
See all httpuv alternatives → · See all Vitest alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Vitest is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Vitest is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top httpuv alternatives in DevOps are ranked by recent ship velocity. Browse the "httpuv alternatives" section above for the current picks, or visit /alternatives/httpuv for the full list with editorial commentary on each.
Top Vitest alternatives in DevOps are ranked by recent ship velocity. Browse the "Vitest alternatives" section above for the current picks, or visit /alternatives/vitest for the full list with editorial commentary on each.