easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of leaflet and tune — release velocity, themes, recent moves, and the top alternatives to consider.
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
leaflet is the R binding for the Leaflet mapping library. Its recent releases are dominated by one long migration: away from sp, rgdal, rgeos and raster, and toward sf and terra. Version 2.2.3 completed the user-facing half of that - sp is no longer installed by default, and bundled datasets ship as sf objects - while also relicensing the package from GPL-2 to MIT.
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
leaflet is the R binding for the Leaflet mapping library. Its recent releases are dominated by one long migration: away from sp, rgdal, rgeos and raster, and toward sf and terra. Version 2.2.3 completed the user-facing half of that - sp is no longer installed by default, and bundled datasets ship as sf objects - while also relicensing the package from GPL-2 to MIT.
This is a package being brought into line with an ecosystem that changed underneath it. The retirement of rgdal and rgeos forced the terra and sf work; the license change and dependency reductions are the maintainers taking the opportunity to clean up while they are already in there. Feature work, such as the full viridisLite palette set, arrives as a side effect of the tidying.
With the sp path now opt-in and the retired geospatial dependencies gone, expect the remaining work to be small: palette and provider-tile handling, and keeping the bundled JavaScript current.
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Other Analytics 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 leaflet or tune.
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
discrim settled into a thin engine shim after handing its model definitions to parsnip.
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
See all leaflet alternatives → · See all tune alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. leaflet and tune are shipping at a similar cadence (velocity 0.0 vs 0.0, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. leaflet and tune are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top leaflet alternatives in Analytics are ranked by recent ship velocity. Browse the "leaflet alternatives" section above for the current picks, or visit /alternatives/leaflet-r for the full list with editorial commentary on each.
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.