LoginSign Up
← Back to all sparks
Q

quarto-r

INFRA · APIS
Velocity0.0

R interface to quarto-cli. Contribute to quarto-dev/quarto-r development by creating an account on GitHub.

github.com/quarto-dev/quarto-r ↗

The R side of Quarto stopped being a render wrapper and became a project interface

quartopublishingcli-wrapperr-packagesreproducible-documents
◆Current state
The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.
◆Where it's heading
The package's job is to stay a faithful surface over a CLI it does not control, and the releases show what that costs. Version numbers track the Quarto release they target, tests are adapted around upstream regressions, and behaviour is reworked when the CLI changes — quarto_use_template() now errors clearly in non-empty directories because interactive prompting was never suitable for programmatic use. The 1.5.1 release exists entirely so CRAN checks pass on machines where Quarto is not installed at all.
◆Prediction
Expect the next release to track the next Quarto CLI version, with the open question in the feed being how --no-prompt behaviour settles upstream for template use. Feature work here follows the CLI rather than leading it.

◆Recent moves

  1. 11mo ago

    Tests skip correctly when Quarto is not installed

    Fixes tests that failed to skip when Quarto was absent, which had broken CRAN checks on macOS and prevented binaries being built, and adds CI coverage for the no-Quarto case. Packaging repair with no behavioural change.

    View source ↗
  2. 1y ago

    output_file moves to Quarto metadata, unlocking multi-format renders

    Changes how quarto_render(output_file =) works: the value now sets the output-file Quarto metadata rather than passing --output on the command line, which sidesteps CLI problems and makes rendering to several output formats in one call possible. Breaking for anyone relying on the flag, though quarto_args gives the old behaviour back. quarto_use_template() also stops relying on interactive prompts and errors clearly in non-empty directories.

    View source ↗
  3. 2y ago

    Preview URL detection fixed inside the RStudio viewer

    Makes quarto_preview() read the preview log to find the right URL when running inside the RStudio viewer, and fixes the approval check in quarto_add_extension() and quarto_use_template(). The package also adopts the x.y.z.dev versioning convention, and adapts tests around a Quarto 1.5.54 regression since fixed upstream.

    View source ↗
  4. 2y ago

    Project, extension and vignette support arrive alongside rendering

    ⚡ SPARK

    Broadens the package from rendering to managing Quarto projects: quarto_create_project(), quarto_add_extension() and quarto_use_template() cover project and extension lifecycle, is_using_quarto() and quarto_binary_sitrep() answer environment questions, and quarto_render() gains profile, metadata and metadata_file arguments. It also registers a vignette engine so R packages can ship .qmd files as vignettes.

    View source ↗