r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of tidymodels and typst-gather — release velocity, themes, recent moves, and the top alternatives to consider.
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.
Release cadence tracks the ecosystem rather than any roadmap of its own: a version bump when member packages release, a tidymodels_prefer() rule when a new conflict appears — DALEX::explains() over dplyr::explains(), recipes::update() over other update() methods. Additions to the core set are the only structurally interesting events, and there have been two in seven releases. Everything else is plumbing that exists so a single library() call attaches a consistent set of versions.
The next release will most likely be another version-set update, with any new core package the only thing worth noting. Feature news for this framework will keep arriving in the member packages, not here.
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
The 0.2.0 restructuring is the tell: subcommands with backwards compatibility, config readable from stdin, and every diagnostic message moved to stderr so stdout carries nothing but JSON. Those are the conventions of a tool meant to be called by another program, not typed by a person. Given its origin inside Quarto's toolchain, the plausible consumer is a build system that needs to know a document's package requirements before deciding what to fetch.
The analyze path currently reports imports; the natural extension visible from here is acting on that report — lockfile output or verification that a cache satisfies a document's dependency set — though the entries do not commit to either.
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 tidymodels or typst-gather.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all tidymodels alternatives → · See all typst-gather alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tidymodels and typst-gather 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. tidymodels and typst-gather 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 tidymodels alternatives in Analytics are ranked by recent ship velocity. Browse the "tidymodels alternatives" section above for the current picks, or visit /alternatives/tidymodels for the full list with editorial commentary on each.
Top typst-gather alternatives in Analytics are ranked by recent ship velocity. Browse the "typst-gather alternatives" section above for the current picks, or visit /alternatives/typst-gather for the full list with editorial commentary on each.