Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Comparison · Infra & APIs
AdGuard Home vs webpack
A side-by-side editorial comparison of AdGuard Home and webpack — release velocity, themes, recent moves, and the top alternatives to consider.
AdGuard Home vs webpack: at a glance
What is AdGuard Home?
AdGuard Home is spending most of its release capacity on DNS protocol vulnerabilities.
Two trains run in parallel: the 0.107.x stable line and a long-running 0.108.0 beta series now at b.90. Security dominates both — one stable release opened by admitting security changes take up over half its changelog. The reported issues cluster in the encrypted-DNS stack: JIGGLE attacks, loose validation of DoH upstream responses, unbounded reads on QUIC connections, DNS-over-QUIC resource exhaustion, and a path traversal in GLiNET-mode authorization. Feature work in the window is minor: comments in bootstrap server configuration, removing a static lease hostname via the HTTP API, day units in YAML durations.
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.
AdGuard Home vs webpack: editorial side-by-side
AdGuard Home
5.0INFRA · APIS
AdGuard Home is spending most of its release capacity on DNS protocol vulnerabilities.
◆ Current state
Two trains run in parallel: the 0.107.x stable line and a long-running 0.108.0 beta series now at b.90. Security dominates both — one stable release opened by admitting security changes take up over half its changelog. The reported issues cluster in the encrypted-DNS stack: JIGGLE attacks, loose validation of DoH upstream responses, unbounded reads on QUIC connections, DNS-over-QUIC resource exhaustion, and a path traversal in GLiNET-mode authorization. Feature work in the window is minor: comments in bootstrap server configuration, removing a static lease hostname via the HTTP API, day units in YAML durations.
◆ Where it's heading
The 0.108 beta has been running long enough that its interesting signal is the edge channel switching to the new UI and versioning scheme — the rewrite is reaching users before the beta closes. Meanwhile the security cadence is community-driven: nearly every fix credits an external reporter, and fixes land in a beta and its stable counterpart within days or the same day. That is a project whose attack surface is its protocol implementations, and whose defence is a fast disclosure-to-patch loop rather than architectural change.
◆ Prediction
Expect the encrypted-DNS transports to keep generating reports and same-week patches on both branches, and the new UI to widen from the edge channel toward beta as 0.108 approaches release.
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 AdGuard Home 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 AdGuard Home 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 AdGuard Home alternatives → · See all webpack alternatives →
Recent activity from AdGuard Home and webpack
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoAdGuard HomeAdGuard Home v0.108.0-b.90
- 6d agowebpackAlias and cache-cleanup fixes after the native-build switch
- 7d agowebpackBun and Deno compatibility fixes, faster HTML parser
- 11d agowebpackTypeScript, CSS and HTML now compile with no loader registered ⚡
- 21d agoAdGuard HomeAdGuard Home v0.108.0-b.89
- 21d agoAdGuard HomeAdGuard Home v0.107.78
- 1mo agowebpackCSS and HTML parsers cut CPU and memory
- 1mo agowebpackHMR codegen crash fix for unresolved harmony imports
- 1mo agowebpackLazy barrel and node: prefix externals fixes
- 2mo agoAdGuard HomeAdGuard Home v0.108.0-b.88
- 2mo agoAdGuard HomeAdGuard Home v0.107.77
- 2mo agoAdGuard HomeAdGuard Home v0.108.0-b.87
Frequently asked questions
What is the difference between AdGuard Home 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 AdGuard Home 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 AdGuard Home?
Top AdGuard Home alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "AdGuard Home alternatives" section above for the current picks, or visit /alternatives/adguard-home 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.