← Back to home
Comparison · Analytics

pkglite vs vcr

A side-by-side editorial comparison of pkglite and vcr — release velocity, themes, recent moves, and the top alternatives to consider.

pkglite vs vcr: at a glance

Featurepkglitevcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-packages, pharma-submissions, packaging, file-handlingtesting, http-mocking, breaking-change, api-cleanup
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is pkglite?

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.

Read the full pkglite trajectory →

What is vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

pkglite vs vcr: editorial side-by-side

P
pkglite
ANALYTICS
0.0

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to pkglite and vcr

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 pkglite or vcr.

See all pkglite alternatives → · See all vcr alternatives →

Recent activity from pkglite and vcr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agopkgliteMaintainer email and CI workflow updates
  2. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  3. 1y agovcrMaintainer email address updated
  4. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  5. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  6. 2y agovcrAdds httr2 support alongside httr and crul
  7. 2y agopkgliteTest helpers moved to helper.R
  8. 3y agovcrDrops compilation; test setup moves back to helper files
  9. 3y agovcrFixes request matching with escaped characters
  10. 3y agopkgliteMore file types recognised; cli dependency dropped
  11. 5y agovcrvcr_test_path() finds the package root correctly
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between pkglite and vcr?

They serve adjacent needs but don't currently overlap on shipped themes. pkglite and vcr 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 pkglite better than vcr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pkglite and vcr 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 pkglite?

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.

What are the best alternatives to vcr?

Top vcr alternatives in Analytics are ranked by recent ship velocity. Browse the "vcr alternatives" section above for the current picks, or visit /alternatives/vcr for the full list with editorial commentary on each.