progressify
0.2.0Progress Reporting of Common Functions via One Magic Function
Overview
The progressify() function rewrites (transpiles) calls to sequential and parallel map-reduce functions such as base::lapply(), purrr::map(), foreach::foreach(), and plyr::llply() to signal progress updates. By combining this function with R's native pipe operator, you have a straightforward way to report progress on iterative computations with minimal refactoring, e.g. 'lapply(x, fcn) |> progressify()' and 'purrr::map(x, fcn) |> progressify()'. It is compatible with the parallel-processing map-reduce packages 'future.apply', 'furrr', 'crossmap', 'foreach', 'doFuture', and 'futurize'. It also supports domain-specific packages including 'boot', 'fwb', 'lme4', 'partykit', 'sandwich', and 'SimDesign', e.g. 'boot::boot(data, stat, R) |> progressify()'.
Significant Changes
- Changed the package license to Apache License (>= 2).
New Features
- Add support for domain-specific CRAN package **boot**, e.g.
res <- boot::boot(data, statistic, R = 100) |> progressify(). - Add support for **crossmap**
future_*()variants, e.g.y <- crossmap::future_xmap(xs, fcn) |> progressify(). - Add support for **furrr** 0.4.0
*_vec()variants:future_map_vec(),future_map2_vec(),future_pmap_vec(), andfuture_imap_vec(). - Add support for domain-specific CRAN package **fwb**, e.g.
res <- fwb::fwb(data, statistic, R = 100) |> progressify().
Show all changes in 0.2.0Hide the rest of the changes in 0.2.0
- Add support for domain-specific CRAN package **lme4**, e.g.
res <- lme4::bootMer(fit, statistic, nsim = 100) |> progressify(). - Add support for
purrr::imap_vec(). - Add support for domain-specific CRAN package **sandwich**, e.g.
v <- sandwich::vcovBS(fit) |> progressify(). - Add support for domain-specific CRAN package **SimDesign**, e.g.
res <- SimDesign::runSimulation(design, replications, generate, analyse, summarise) |> progressify().
From NEWS.md in the release
Install
Health
- OK13 OK2026-08-05
- NOTE12 OK, 1 NOTE2026-08-01
- OK13 OK2026-06-08
- NOTE12 OK, 1 NOTE2026-06-07
- OK6 OK2026-04-08
Documentation
- Help pages
- 3 (1 internal)
- Examples that run
- 100%2 run in a plain check
- Exported functions with examples
- 100%
- Documented parameters
- 100%
- Return-value docs
- 100%
- Help pages citing references
- 0%
- Progress updates for 'boot' functions
- Progress updates for 'crossmap' functions
- Progress updates for 'foreach' functions
- Progress updates for 'furrr' functions
- Progress updates for 'future.apply' functions
- Progress updates for 'fwb' functions
- Progress updates for 'lme4' functions
- Progress updates for 'partykit' functions
- Progress updates for 'plyr' functions
- Progress updates for 'purrr' functions
Downloads
Repository
- PRs merged (all time)
- not measured
- Median days to close, 50 most recently updated closed issues
- 0
- Median days to close, 50 most recently updated closed PRs
- not measured
Stars over time
Issues over time
Commits over time
8 development-tooling and community-health practices detected across 5 families in the upstream repository
Checks run against github.com/futureverse/progressify on 2026-10-11.
The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel
Show all practicesHide 1 practice
Dependencies
Installing progressify adds 2 packages (1 with compiled code, 766 KB of source tarballs). Heaviest: progressr 535 KB, digest 231 KB.
Code & Tests
People & History
Pick two releases to compare their code metrics.
- 0.2.0Latest
- RR 4.6.0 released · 2026-04-24
- 0.1.02026-04-07
- RR 4.5.0 released · 2025-04-11
Package metadata
- First published
- 2026-04-07
- Total releases
- 2 / 1 yrs
- License
- Apache License (>= 2) · relicensed from GPL (>= 3) in 0.2.0
- Minimum R
- ≥ 4.1.0
- Download size
- 118 KB
Cite
Cite this package
Run in R for the authors' preferred citation:
citation("progressify")This package has no citation file, so citation() returns this entry built from DESCRIPTION.
Cite the R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
From data release v2026-10-17, which the citation names so these numbers can be found later. More on citing and the projects behind them.