kwb.pkgbuild
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
A side-by-side editorial comparison of rdocdump and rextendr — release velocity, themes, recent moves, and the top alternatives to consider.
rdocdump grew from a CRAN doc dumper into a resolver that pulls packages from anywhere
rdocdump flattens an R package's documentation and source into plain text, a shape aimed squarely at feeding code and docs to language models. It reached CRAN in June 2025 handling CRAN packages only. Within a year it accepted GitHub, GitLab and Bitbucket references with branch, tag and commit pinning, and 0.3.0 in May 2026 moved resolution onto pak.
rextendr put Rust-backed R packages in the browser, then tore itself down for a 1.0.0 rebuild
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
rdocdump flattens an R package's documentation and source into plain text, a shape aimed squarely at feeding code and docs to language models. It reached CRAN in June 2025 handling CRAN packages only. Within a year it accepted GitHub, GitLab and Bitbucket references with branch, tag and commit pinning, and 0.3.0 in May 2026 moved resolution onto pak.
The direction is to stop caring where a package lives. 0.2.0 opened remote repository references and direct URLs; 0.3.0 swapped remotes for pak, added auto-discovery of packages in subdirectories, broadened URL format support to Bioconductor and GitLab, and added git clone as an automatic fallback when resolution fails. Cross-platform handling moved to internal tar operations.
With resolution generalized, remaining work is likely on output shaping — what gets included and how it is chunked — rather than on more sources. The entries do not say whether the text output format itself is stable.
rextendr is the R-side toolchain for extendr, scaffolding and compiling R packages with Rust internals. The package is mid-teardown: the 0.4-final tag in October 2025 warns that main may not work as expected and directs users to install from that tag, and April 2026's release is titled as one more developer release before 1.0.0. Meanwhile the CRAN-facing 0.4.x line did the substantive work.
Two threads run in parallel. The first is reach: 0.4.0 added WebR support out of the box for all extendr packages by enabling the wasm32-unknown-emscripten target, and 0.4.2 followed with the panic and link-time-optimization settings needed to make those builds actually work. The second is CRAN compliance — use_cran_defaults(), vendor_pkgs(), automatic SystemRequirements fields, and configure scripts, all aimed at getting Rust-powered packages accepted on CRAN. The rebuild announced in 0.4-final is a third thread whose shape the entries do not reveal.
The stated destination is 1.0.0 built on the new Makevars-linked build process, so that release is the next milestone. What the revamp changes for existing extendr packages is not described in any entry here.
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 rdocdump or rextendr.
kwb.pkgbuild's CI templates went four years without a refresh, then had to be rebuilt for current runners
saperlipopette turned Git disasters into practice exercises, then passed peer review
nominatimlite's real work was self-hosting and caching; 0.6.0 is an internal refactor with no API change
osrm.backend stopped trusting upstream binaries and started shipping its own
taxifydb found that its coverage audit was checking a hand-maintained list, not reality.
A code generator that turns an OpenAPI spec into a working R client package, milestone by milestone.
See all rdocdump alternatives → · See all rextendr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Infra & APIs. rdocdump and rextendr 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. rdocdump and rextendr 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 Infra & APIs products to evaluate alongside.
Top rdocdump alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rdocdump alternatives" section above for the current picks, or visit /alternatives/rdocdump for the full list with editorial commentary on each.
Top rextendr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rextendr alternatives" section above for the current picks, or visit /alternatives/rextendr for the full list with editorial commentary on each.