# shinylive 0.5.0

## Bug fixes and minor improvements

* Updated the default shinylive assets to
  [v0.10.12](https://github.com/posit-dev/shinylive/releases/tag/v0.10.12),
  which upgrades the bundled webR to
  [v0.6.0](https://github.com/r-wasm/webr/releases/tag/v0.6.0) (#193, #195).

* WebAssembly package binaries cached during `export()` are now replaced once
  the WebAssembly repository catches up to the locally installed version.
  Previously, a binary downloaded while the repository lagged behind was never
  refreshed (#194).

# shinylive 0.4.1

## Bug fixes

* Fixed CRAN policy violation where tests could create the shinylive
  assets cache directory (`~/.cache/shinylive` or
  `~/Library/Caches/shinylive` on macOS). Tests that interact with the
  cache are now skipped on CRAN, and `assets_cache_dir()` includes a
  runtime guard that errors if called during CRAN testing
  (#185, #186).

# shinylive 0.4.0

## Lifecycle changes

* `export(verbose=)` now signals its deprecation warning using
  `lifecycle::deprecate_warn()`. `verbose` was soft-deprecated in
  shinylive 0.2.0 in favor of `quiet` (#182).

## New features

* `export()` now displays `{cli}` progress bars when downloading
  WebAssembly packages (#169).

## Bug fixes and minor improvements

* Updated default shinylive assets to
  [v0.10.8](https://github.com/posit-dev/shinylive/releases/tag/v0.10.8)
  (#165, #166, #177).

* `export()` no longer produces an encoding error when exporting certain
  apps (#118, #172), now uses HTTPS when downloading WebAssembly packages
  (#171), and no longer warns when an app has zero package dependencies
  (#172).

# shinylive 0.3.0

* Updated default shinylive assets to [v0.9.1](https://github.com/posit-dev/shinylive/releases/tag/v0.9.1). (#120, #129, #135)

* Resources are now built relative to Quarto project root. (#130)

* In CI and other automated workflow settings the `SHINYLIVE_WASM_PACKAGES` environment variable can now be used to control whether WebAssembly R package binaries are bundled with the exported shinylive app, in addition to the `wasm_packages` argument of the `export()` function. (#116)

* shinylive now avoids bundling WebAssembly R package dependencies listed only in the `LinkingTo` section of required packages. With this change dependencies that are only required at build time are no longer included as part of the exported WebAssembly asset bundle. This reduces the total static asset size and improves the loading time of affected shinylive apps. (#115)

* shinylive now supports adding files in virtual subdirectories in `shinylive-r` apps embedded in Quarto documents. For example, `## file: R/load_data.R` in a `shinylive-r` chunk followed by the `load_data.R` code will create a file `load_data.R` in the `R` subdirectory of the exported app. (#119)

# shinylive 0.2.0

* shinylive now uses [shinylive web assets v0.5.0](https://github.com/posit-dev/shinylive/releases/tag/v0.5.0) by default, which bundles webR 0.4.0 with R 4.4.1. This update brings improved keyboard shortcuts for R users in the Shinylive editor, the ability to export a custom library of R packages with the exported app, and a few improvements to the Quarto integration. (#108)

* `export()` gains an `assets_version` argument to choose the version of the Shinylive web assets to be used with the exported app. This is primarily useful for testing new versions of the Shinylive assets before they're officially released via a package update. In CI and other automated workflow settings, the `SHINYLIVE_ASSETS_VERSION` environment variable can be used to set the assets version. (#91)

* `export()` gains `template_params` and `template_dir` arguments to control the template HTML files used in the export, allowing users to partially or completely customize the exported HTML. The export template is provided by the shinylive assets and may change from release-to-release. Use `assets_info()` to locate installed shinylive assets; the template files for a given release are in the `export_template` directory of the release. (#96)
    * `template_params` takes a list of parameters to be interpolated into the template. The default template include `title` (the title for the page with the exported app), `include_in_head` (HTML added to the `<head>` of the page), and `include_before_body` (HTML added just after `<body>`) and `include_after_body` (HTML added just after `</body>`).
    * `template_dir` is the directory containing the template files. The default is the `export_template` directory of the shinylive assets being used for the export. Use `assets_info()` to locate installed shinylive assets where you can find the default template files.

* shinylive now uses `{cli}` for console printing. Console output can be suppressed via the global R option by calling `options(shinylive.quiet = TRUE)`. (#104)

* `export()` and `assets_info()` gain a `quiet` argument. In `export()`, `quiet` replaces the now-deprecated `verbose` option, which continues to work with a warning. (#104)

# shinylive 0.1.1

* Bump shinylive assets dependency to 0.2.3. (#38)

* Use `{httpuv}` to serve static folder instead of plumber. (#40)

* Use `{httr2}` to download assets from GitHub releases. (@dgkf #30, #39)

# shinylive 0.1.0

* Initial CRAN submission.
