tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
fellingdater vs webmockr
A side-by-side editorial comparison of fellingdater and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropensci
fellingdater vs webmockr: at a glance
What is fellingdater?
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.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
fellingdater vs webmockr: editorial side-by-side
fellingdater
0.0ANALYTICS
Went from estimating felling dates to doing the crossdating that produces them.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to fellingdater and webmockr
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 webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all fellingdater alternatives → · See all webmockr alternatives →
Recent activity from fellingdater and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agofellingdaterPolish for the crossdating plots and file reader
- 1y agowebmockrvcr dependency severed
- 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit ⚡
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agofellingdaterUser-supplied sapwood data works across all functions
- 1y agofellingdaterFixes fd_report() with user-defined sapwood files
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 2y agofellingdaterJOSS paper accepted; citation updated
- 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between fellingdater and webmockr?
Both compete on the same themes — ropensci — within Analytics. fellingdater and webmockr 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.
Is fellingdater better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fellingdater and webmockr 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.
What are the best alternatives to fellingdater?
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.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.