← Back to home
Comparison · Infra & APIs

webpack vs Dashy

A side-by-side editorial comparison of webpack and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.

webpack vs Dashy: at a glance

FeaturewebpackDashy
SectorInfra & APIsInfra & APIs
Velocity score6.36.3
Sparks · 30d11
Top themeszero-config, native-typescript, loader-consolidation, parser-performanceself-hosted, dashboard, drag-and-drop, widgets
Last editorial update1d ago1h ago
WebsiteVisit →Visit →

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.

Read the full webpack trajectory →

What is Dashy?

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.

Read the full Dashy trajectory →

webpack vs Dashy: editorial side-by-side

W
webpack
INFRA · APIS
6.3

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.

D
Dashy
INFRA · APIS
6.3

The self-hosted dashboard finally let you drag things around instead of editing YAML.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to webpack and Dashy

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.

See all webpack alternatives → · See all Dashy alternatives →

Recent activity from webpack and Dashy

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoDashyMissing German translations added
  2. 3d agoDashyOut-of-memory crash from unclosed secureConnect listeners fixed
  3. 4d agoDashyDependency bumps in the minor-and-patch group
  4. 6d agoDashyOIDC post-logout redirect URI support
  5. 6d agowebpackAlias and cache-cleanup fixes after the native-build switch
  6. 7d agowebpackBun and Deno compatibility fixes, faster HTML parser
  7. 8d agoDashyItems can be sorted by provider and by item ID
  8. 9d agoDashy4.5.0 adds drag-and-drop editing of sections, items and widgets
  9. 11d agowebpackTypeScript, CSS and HTML now compile with no loader registered
  10. 1mo agowebpackCSS and HTML parsers cut CPU and memory
  11. 1mo agowebpackHMR codegen crash fix for unresolved harmony imports
  12. 1mo agowebpackLazy barrel and node: prefix externals fixes

Frequently asked questions

What is the difference between webpack and Dashy?

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.

Is webpack better than Dashy?

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.

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.

What are the best alternatives to Dashy?

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.