posit-dev / posit-dev/shinylive
Set up official shinylive.io with dev Shiny for Python and R
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 251
- Forks
- 25
- Avg merge
- 19m
- Merged PRs (30d)
- 2
Description
We could build a version of shinylive on a nightly cadence that uses
- Production shinylive.io
posit-dev/py-shiny@mainrstudio/shiny@main
It'd be especially helpful if users could switch between these versions by adding dev somewhere in the URL, e.g.
https://dev.shinylive.io/py/editororhttps://shinylive.io/dev/py/editororhttps://shinylive.io/py/dev/editor.
This intersects with the Shiny extension for VS Code in two ways:
-
We currently advertise
https://posit-dev.github.io/shinyliveas the host for "dev" shinylive. We should update the list of hosts here. -
We currently assume that the language is the second part of the path, but this can easily be adjusted.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed dev-host options and the referenced shiny-vscode files: package.json lines 194-206 and src/shinylive.ts lines 544-550. Define how nightly builds use the Shiny main branches and how users select them by URL; done means the dev host works and the VS Code host and path assumptions match it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r, typescript, wasm
- Domain
- developer-experience, devops, infrastructure, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100