You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that at app startup renv searches for packages inside the Shinylive app. Then, we then download each of them from the default webR binary repository. However, we might not want to download all packages from the default repo -- we might want to load them from a personal repo built with r-wasm/actions, R Universe, or somewhere else entirely.
We should have some way to signal to Shinylive that we have a package from a custom repository we want to load. Some immediate options come to mind, in order of my personal preference.
Setup a new user library at startup so that webr::install() has priority over packages that are downloaded automatically.
Somehow allow for defining a custom repository list for the automatic package download system.
Document that automatic packages can be removed with webr::unmount() (P.S. Should we shim remove.packages() to do this in any case?)
Note: This issue should not affect Python apps. R apps deployed with shinylive::export() will be unaffected going forward, since in a future releases of r-shinylive the shinylive::export() function will gather the package references for packages installed on the local machine and deploy them directly with the app.
The text was updated successfully, but these errors were encountered:
I think the best way to handle bioconductor is in the Shinylive R package. We should detect bioconductor packages and download the associated Wasm binary from R-Universe, even if the package has been installed from the official bioconductor repo.
See discussion in r-wasm/actions#18 for details.
The issue is that at app startup
renv
searches for packages inside the Shinylive app. Then, we then download each of them from the default webR binary repository. However, we might not want to download all packages from the default repo -- we might want to load them from a personal repo built with r-wasm/actions, R Universe, or somewhere else entirely.The relevant R code:
shinylive/src/hooks/useWebR.tsx
Lines 256 to 267 in 6afcdc8
We should have some way to signal to Shinylive that we have a package from a custom repository we want to load. Some immediate options come to mind, in order of my personal preference.
webr::install()
has priority over packages that are downloaded automatically.webr::unmount()
(P.S. Should we shimremove.packages()
to do this in any case?)Note: This issue should not affect Python apps. R apps deployed with
shinylive::export()
will be unaffected going forward, since in a future releases of r-shinylive theshinylive::export()
function will gather the package references for packages installed on the local machine and deploy them directly with the app.The text was updated successfully, but these errors were encountered: