RSS-Bridge
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
A side-by-side editorial comparison of webpack and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
webpack 5.109 flips experiments.typescript, experiments.css, experiments.html and experiments.asyncWebAssembly to "auto", so a project on Node 22.6+ compiles TypeScript, CSS and HTML with no loader registered at all. The same release adds built-in build progress via infrastructureLogging.progress, resource hints (preload/prefetch/modulepreload/preconnect) on by default for ESM output, and CommonJS module concatenation. Underneath, the 5.108 line is a sustained parser-performance campaign — struct-of-arrays HTML ASTs, dropped unused CSS value tokens, lower peak memory.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
webpack 5.109 flips experiments.typescript, experiments.css, experiments.html and experiments.asyncWebAssembly to "auto", so a project on Node 22.6+ compiles TypeScript, CSS and HTML with no loader registered at all. The same release adds built-in build progress via infrastructureLogging.progress, resource hints (preload/prefetch/modulepreload/preconnect) on by default for ESM output, and CommonJS module concatenation. Underneath, the 5.108 line is a sustained parser-performance campaign — struct-of-arrays HTML ASTs, dropped unused CSS value tokens, lower peak memory.
The direction is unmistakable: webpack is deleting the reason its configs became notorious. Every capability that used to require ts-loader, css-loader or html-webpack-plugin is being pulled into core and defaulted on, which is the only credible answer to zero-config rivals that never asked users to assemble a loader chain. Alongside that, a bun target and repeated Bun/Deno compatibility guards show webpack no longer assumes Node is the only runtime it must run under.
Expect the "auto" experiments to graduate out of the experiments namespace into stable top-level options, and expect the loader-shaped surface area to keep shrinking as more of the pipeline lands in core.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
The direction is away from configuration-as-a-file toward direct manipulation, which is the friction that has always separated Dashy from simpler homepage dashboards. The supporting work lines up with it: sorting controls, better handling of long titles, richer widget formatting. The auth-adjacent changes — OIDC logout redirect, logout destination — suggest people are running Dashy behind an identity provider for more than one user.
With drag-and-drop editing shipped, the follow-on is most likely persistence and permissions questions around who can edit a shared dashboard, though these notes do not state that. Expect the per-PR release cadence to continue producing mostly dependency tags.
Other Infra & APIs 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 webpack or Dashy.
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
See all webpack alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. webpack and Dashy are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. webpack and Dashy are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top webpack alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "webpack alternatives" section above for the current picks, or visit /alternatives/webpack for the full list with editorial commentary on each.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.