r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of fellingdater and pkglite — release velocity, themes, recent moves, and the top alternatives to consider.
Went from estimating felling dates to doing the crossdating that produces them.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
The package has expanded backwards along the workflow. It began at the last step — given dated series, estimate the felling date — and 1.2.0 added the step before it, establishing those dates by crossdating in the first place. Version 1.2.1 is early polish on that new surface: axis control, non-syntactic column names, encoding safety in read_fh(). The direction is a single package covering the chain from raw ring widths to a felling-date estimate.
Expect the trs_* family to keep accumulating polish and additional crossdating statistics, since it is barely a year old and 1.2.1 was already fixing its plotting and top_n behaviour. Whether the two halves of the package get unified into one workflow interface is the open question the entries do not answer.
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.
Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.
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 fellingdater or pkglite.
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 fellingdater alternatives → · See all pkglite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fellingdater and pkglite 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. fellingdater and pkglite 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 fellingdater alternatives in Analytics are ranked by recent ship velocity. Browse the "fellingdater alternatives" section above for the current picks, or visit /alternatives/fellingdater for the full list with editorial commentary on each.
Top pkglite alternatives in Analytics are ranked by recent ship velocity. Browse the "pkglite alternatives" section above for the current picks, or visit /alternatives/pkglite for the full list with editorial commentary on each.