Retool
Retool is retiring standalone Assist while folding the same capability into the app builder.
Comparison · Infra & APIs
rgm vs webpack
A side-by-side editorial comparison of rgm and webpack — release velocity, themes, recent moves, and the top alternatives to consider.
rgm vs webpack: at a glance
What is rgm?
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.
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.
rgm vs webpack: editorial side-by-side
rgm
0.0INFRA · APIS
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
◆ Current state
rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.
◆ Where it's heading
Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.
◆ Prediction
The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.
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 rgm 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 rgm or webpack.
WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
Recent activity from rgm and webpack
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agowebpackAlias and cache-cleanup fixes after the native-build switch
- 22d agowebpackBun and Deno compatibility fixes, faster HTML parser
- 26d agowebpackTypeScript, CSS and HTML now compile with no loader registered ⚡
- 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
- 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
- 3mo agorgmBack on CRAN after dropping the dependency that caused archival
- 3mo agorgmUnreleased twin of the CRAN recovery release
- 2y agorgmFirst release: simulation, estimation and post-processing
Frequently asked questions
What is the difference between rgm and webpack?
They serve adjacent needs but don't currently overlap on shipped themes. webpack is currently shipping more aggressively (velocity 6.3 vs 0.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 rgm 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 0.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 rgm?
Top rgm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rgm alternatives" section above for the current picks, or visit /alternatives/rgm 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.