← Back to home
Comparison · Analytics

pkglite vs webmockr

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

pkglite vs webmockr: at a glance

Featurepkglitewebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-packages, pharma-submissions, packaging, file-handlinghttp-mocking, testing, httr2, ropensci
Last editorial update1h ago45m 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 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.

Read the full webmockr trajectory →

pkglite vs webmockr: 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.

W
webmockr
ANALYTICS
0.0

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

See all pkglite alternatives → · See all webmockr alternatives →

Recent activity from pkglite and webmockr

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

  1. 5mo agopkgliteMaintainer email and CI workflow updates
  2. 1y agowebmockrvcr dependency severed
  3. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  4. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  5. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  6. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  7. 2y agowebmockrhttr2 joins httr and crul as a supported client
  8. 2y agopkgliteTest helpers moved to helper.R
  9. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  10. 3y agopkgliteMore file types recognised; cli dependency dropped
  11. 3y agowebmockrRegex URI matching fixed
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between pkglite and webmockr?

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

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