← Back to home
Comparison · Analytics

pkglite vs textshaping

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

pkglite vs textshaping: at a glance

Featurepkglitetextshaping
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-packages, pharma-submissions, packaging, file-handlingtypography, text-shaping, bidi, graphics-stack
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 textshaping?

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

Read the full textshaping trajectory →

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

T
textshaping
ANALYTICS
0.0

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

◆ Current state

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

◆ Where it's heading

The package has moved from Latin-first layout to script-agnostic layout in two rewrites, 0.4.0 and 1.0.0, and is now in the long correctness tail that follows. The bug reports arriving from ggplot2, ragg and marquee issue numbers show how it works in practice: textshaping bugs surface as rendering defects in the packages above it, which is why so many fixes here cite another package's issue tracker.

◆ Prediction

Expect continued fixes driven by downstream rendering reports rather than new layout features, as the 1.0.x series stabilises. The font fallback path has produced two of the recent bugs and is the most likely source of the next.

Alternatives to pkglite and textshaping

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 textshaping.

See all pkglite alternatives → · See all textshaping alternatives →

Recent activity from pkglite and textshaping

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

  1. 5mo agotextshapingFixes reverting between font fallbacks
  2. 5mo agopkgliteMaintainer email and CI workflow updates
  3. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  4. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  5. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  6. 1y agotextshapingFixes hard line breaks across multiple embeddings
  7. 1y agotextshapingShaping engine rewritten to honour global text direction
  8. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  9. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  10. 2y agopkgliteTest helpers moved to helper.R
  11. 3y agopkgliteMore file types recognised; cli dependency dropped
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between pkglite and textshaping?

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

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

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