← Back to home
Comparison · Analytics

textshaping vs webmockr

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

textshaping vs webmockr: at a glance

Featuretextshapingwebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestypography, text-shaping, bidi, graphics-stackhttp-mocking, testing, httr2, ropensci
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

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 →

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 →

textshaping vs webmockr: editorial side-by-side

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.

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

See all textshaping alternatives → · See all webmockr alternatives →

Recent activity from textshaping and webmockr

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

  1. 5mo agotextshapingFixes reverting between font fallbacks
  2. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  3. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  4. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  5. 1y agowebmockrvcr dependency severed
  6. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  7. 1y agotextshapingFixes hard line breaks across multiple embeddings
  8. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  9. 1y agotextshapingShaping engine rewritten to honour global text direction
  10. 2y agowebmockrhttr2 joins httr and crul as a supported client
  11. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  12. 3y agowebmockrRegex URI matching fixed

Frequently asked questions

What is the difference between textshaping and webmockr?

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

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

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.