Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
carrier vs packrat
A side-by-side editorial comparison of carrier and packrat — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
carrier vs packrat: at a glance
What is carrier?
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
What is packrat?
R's old dependency manager now runs on a vendored copy of its own successor.
packrat was R's project dependency manager before renv replaced it, and its recent releases describe a package in careful retirement. It vendors renv internally and uses it for dependency detection and authenticated downloads, so several release notes amount to updating that bundled copy. The remaining work is repository plumbing: recognising Bioconductor packages that now carry a Repository field, handling CRAN-like, Nexus and older Artifactory archive layouts, and renaming downloads from r-universe that do not follow the expected filename pattern.
carrier vs packrat: editorial side-by-side
carrier
0.0INFRA · APIS
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
◆ Current state
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
◆ Where it's heading
Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.
◆ Prediction
The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.
packrat
0.0INFRA · APIS
R's old dependency manager now runs on a vendored copy of its own successor.
◆ Current state
packrat was R's project dependency manager before renv replaced it, and its recent releases describe a package in careful retirement. It vendors renv internally and uses it for dependency detection and authenticated downloads, so several release notes amount to updating that bundled copy. The remaining work is repository plumbing: recognising Bioconductor packages that now carry a Repository field, handling CRAN-like, Nexus and older Artifactory archive layouts, and renaming downloads from r-universe that do not follow the expected filename pattern.
◆ Where it's heading
Development here is about keeping existing projects restorable rather than making packrat a better choice for new ones. Nearly every entry is a fix for an environment that changed underneath it — a repository layout, a service's authentication scheme, a distribution's URL format. The vendoring of renv is the clearest statement of direction: the successor's logic is doing the work, wrapped in the old interface.
◆ Prediction
Expect further releases only when package repositories change shape or the vendored renv needs refreshing, at roughly the two-year cadence the recent history shows. Nothing suggests new capability, and the practical migration path remains renv itself.
Alternatives to carrier and packrat
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 carrier or packrat.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
See all carrier alternatives → · See all packrat alternatives →
Recent activity from carrier and packrat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agocarrierCrated helper functions can now see each other ⚡
- 1y agocarriercrate() gains .parent_env and stricter argument handling
- 1y agopackratHandles Bioconductor detection and varied repository layouts
- 3y agocarrierSource references dropped from crated functions
- 3y agopackratRestores packages installed from repository subdirectories
- 3y agopackratPrivate repository restores; git credentials masked from installs
- 4y agopackratGitLab private repos authenticate via GITLAB_PAT
- 4y agopackratBundles renv for dependency detection; adds authenticated downloads
- 4y agocarrierInitial release with explicit-only crate packing
- 4y agopackratBreaking: cache directory now includes an R version suffix
Frequently asked questions
What is the difference between carrier and packrat?
Both compete on the same themes — r-package — within Infra & APIs. carrier and packrat 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 carrier better than packrat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. carrier and packrat 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.
What are the best alternatives to carrier?
Top carrier alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "carrier alternatives" section above for the current picks, or visit /alternatives/carrier for the full list with editorial commentary on each.
What are the best alternatives to packrat?
Top packrat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "packrat alternatives" section above for the current picks, or visit /alternatives/packrat for the full list with editorial commentary on each.