Skip to content

Commit

Permalink
docs: Remove {renv} from package discovery section (#100)
Browse files Browse the repository at this point in the history
It can be confusing (does the app need to use renv?) and it's an internal implementation detail
that isn't broadly useful to users.

Fixes #84
  • Loading branch information
gadenbuie authored Jul 1, 2024
1 parent 5b1cebe commit 71a540e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,9 +73,9 @@ For more information, see the [examples folder](https://github.com/posit-dev/r-s

## R package availability

The `{shinylive}` web assets will statically inspect which packages are being used via `{renv}`.
The `{shinylive}` web assets will statically inspect which packages are being used in your app.

If you need a package that can not be found by `{renv}`, add an impossible-to-reach code within your Shiny application that has a library call to that R package. For example:
If your app includes a package that is not automatically discovered, you can add an impossible-to-reach code within your Shiny application that has a library call to that R package. For example:

```r
if (FALSE) {
Expand Down

0 comments on commit 71a540e

Please sign in to comment.