Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Comparison · Infra & APIs
Dragonfly vs webpack
A side-by-side editorial comparison of Dragonfly and webpack — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs webpack: at a glance
What is Dragonfly?
Dragonfly is paying down its Redis fork debt and chasing correctness in the new IO loop.
Releases land every few days as incremental i1.39.x tags, and the work splits three ways. First, resyncing forked Redis code with upstream Valkey — the hyperloglog resync pulled in a CVE fix for run-length overflow in sparse opcodes plus AVX2 and ARM NEON merge kernels, and exposed three Dragonfly-local bugs in the process. Second, correctness in the v1 and v2 IO loops: a pub/sub ordering defect where anti-starvation quota logic could run a pipelined UNSUBSCRIBE ahead of queued messages and silently drop them. Third, ongoing internal migration of command handlers to a new argument parser.
What is webpack?
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.
Dragonfly vs webpack: editorial side-by-side
Dragonfly
5.0INFRA · APIS
Dragonfly is paying down its Redis fork debt and chasing correctness in the new IO loop.
◆ Current state
Releases land every few days as incremental i1.39.x tags, and the work splits three ways. First, resyncing forked Redis code with upstream Valkey — the hyperloglog resync pulled in a CVE fix for run-length overflow in sparse opcodes plus AVX2 and ARM NEON merge kernels, and exposed three Dragonfly-local bugs in the process. Second, correctness in the v1 and v2 IO loops: a pub/sub ordering defect where anti-starvation quota logic could run a pipelined UNSUBSCRIBE ahead of queued messages and silently drop them. Third, ongoing internal migration of command handlers to a new argument parser.
◆ Where it's heading
The fork-maintenance thread is the structural one — Dragonfly carries Valkey-derived code that drifts, and resyncing is how it inherits both security fixes and SIMD performance work it did not write. Running two IO loop generations at once is the current source of risk, visible in tests that had to be skipped on the v1 leg and in an ordering bug that only appeared after v1.38 changed the dispatch quota. Neither thread is adding user-facing capability; this is a window of consolidation.
◆ Prediction
Expect the v2 IO loop to move toward default as the ordering and pause-semantics gaps close, and further upstream resyncs of forked Redis files now that the hyperloglog sync established a formatting convention to keep them cheap.
webpack
6.3INFRA · APIS
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Dragonfly and webpack
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 Dragonfly or webpack.
RSS-Bridge
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
Jackett
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Sonarr
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
k0s
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
See all Dragonfly alternatives → · See all webpack alternatives →
Recent activity from Dragonfly and webpack
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
- 6d agowebpackAlias and cache-cleanup fixes after the native-build switch
- 7d agowebpackBun and Deno compatibility fixes, faster HTML parser
- 11d agoDragonflyFix mutable cross-thread access on shared reply builder
- 11d agowebpackTypeScript, CSS and HTML now compile with no loader registered ⚡
- 13d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
- 26d agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
- 1mo agowebpackCSS and HTML parsers cut CPU and memory
- 1mo agoDragonflyi1.39.4: Add list compression tuning flags (#7762)
- 1mo agowebpackHMR codegen crash fix for unresolved harmony imports
- 1mo agowebpackLazy barrel and node: prefix externals fixes
- 1mo agoDragonflyi1.39.3: chore(server): migrate main_service handlers to CmdArgParser
Frequently asked questions
What is the difference between Dragonfly and webpack?
They serve adjacent needs but don't currently overlap on shipped themes. webpack is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Is Dragonfly better than webpack?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. webpack is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Dragonfly?
Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.
What are the best alternatives to webpack?
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.