Thanos
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
A side-by-side editorial comparison of Casdoor and webpack — release velocity, themes, recent moves, and the top alternatives to consider.
Ten releases in 48 hours, nearly all of them tightening who can do what, for how long
Casdoor is shipping a one-feature-per-release train at extreme cadence — ten tagged versions across two days, each carrying a single commit. The subject matter is unusually concentrated: seven of the last ten entries touch authorization, session lifetime, or OAuth protocol conformance rather than the UI or the connector surface. What used to be an SSO front-end with a Casbin engine behind it is being reworked at the permission layer itself.
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.
Casdoor is shipping a one-feature-per-release train at extreme cadence — ten tagged versions across two days, each carrying a single commit. The subject matter is unusually concentrated: seven of the last ten entries touch authorization, session lifetime, or OAuth protocol conformance rather than the UI or the connector surface. What used to be an SSO front-end with a Casbin engine behind it is being reworked at the permission layer itself.
The direction is from standing access toward time-bounded, audience-scoped access. Permissions now carry a configurable expiry that revokes them automatically, token retention is set per organization instead of globally, and the OAuth path preserves RFC 8707 resource indicators so tokens can be bound to a specific target rather than the whole deployment. Alongside that, the enforcement path is being made cheaper — a batch permission API exists specifically to stop rebuilding the Casbin enforcer per call — which is what you build when permission churn stops being an admin-scale event.
Expect the expiry work to grow into a policy surface rather than a single field — per-role or per-application default TTLs, and an audit view of what expired when. The batch API and the RFC 8707 handling point the same way, so a first-class machine or service-identity flow is the plausible next step, though nothing in these entries names it directly.
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.
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 Casdoor or webpack.
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
CAS 8.0 is six release candidates deep with notes that describe nothing
LibreELEC's changelog stops dead at the 12.0 release in May 2024
Node-RED 5.0 rebuilt the editor, and the patches since are settling it in
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
Biome's patch train is really a type-aware linting project in disguise
See all Casdoor alternatives → · See all webpack alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.
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.