shinyreact 
shinyreact lets you write the UI of a Shiny for Python app as a React client you own, while the Python server contains only reactive computation. It provides the bridge between the two and ships zero UI components itself. The same JavaScript bundle backs the R package, so one React client works against an app.py or an app.R server. The full site covers all three.
Installation
pip install shinyreact
Or install the development version from GitHub:
pip install "git+https://github.com/posit-dev/shinyreact.git"
Usage
set_react_page() discovers www/ui.js (and www/ui.css, if present) next to the app file and serves them as the page. @reactive_output publishes any JSON-serializable value to the client's useShinyOutputValue() hook:
from shiny.express import input
from shinyreact import reactive_output, set_react_page
set_react_page()
@reactive_output
def greeting():
return f"Hello, {input.name()}!"
In Core mode, page_react() is the ui argument instead:
from shiny import App
from shinyreact import page_react, reactive_output
def server(input, output, session):
@reactive_output
def greeting():
return f"Hello, {input.name()}!"
app = App(page_react(), server)
The matching www/ui.js:
const { React, ReactDOM, useShinyInput, useShinyOutputValue } = window.shinyreact;
const h = React.createElement;
function App() {
const [name, setName] = useShinyInput("name", "world");
const greeting = useShinyOutputValue("greeting");
return h(
"div",
null,
h("input", { value: name, onChange: (e) => setName(e.target.value) }),
h("p", null, greeting)
);
}
ReactDOM.createRoot(document.body.appendChild(document.createElement("div"))).render(h(App));
Try a complete app:
git clone https://github.com/posit-dev/shinyreact
shiny run shinyreact/examples/01-hello/app.py
Learn more
- Get started walks through the
ui.tsxpattern: inputs, outputs, messages, and embedding traditional Shiny renderers. - TSX files and JavaScript build tools explains
.tsx, JSX, TypeScript, and whatnpm run builddoes. - Client hooks lists everything at
window.shinyreact. - Testing covers shiny's
local_serverpytest fixture for driving a server with no browser, andWireTapfor wire payloads in Playwright tests. - Agent Skills explains the skills that ship with the package for coding agents.
- The examples catalog lists runnable apps from no-build to Vite + HMR.
Metadata
Release files for shinyreact 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| shinyreact-0.1.0.tar.gz | 114.1 kB | With provenance | Details for shinyreact-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| shinyreact-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for shinyreact-0.1.0-py3-none-any.whl |
Total release size: 236.1 kB
Release files / shinyreact-0.1.0.tar.gz
| Download URL | shinyreact-0.1.0.tar.gz |
|---|---|
| Size | 114.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3df1d2f844fa5d3a070738611fa334796e56122e69e2b48f9dd024228403eb97
|
|
BLAKE2b-256 checksum How to use checksums |
1491dfc7ababee605370df61e364bda38c8600d5fe9fb2ee010fbf39ce209093
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logRelease files / shinyreact-0.1.0-py3-none-any.whl
| Download URL | shinyreact-0.1.0-py3-none-any.whl |
|---|---|
| Size | 122.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31d5c69787274b6455e94386c082e6cc76b0b0526dcd2972029d64b930453962
|
|
BLAKE2b-256 checksum How to use checksums |
ad02c9b5e49461026eedd5728c91fa8e5ef3eb292f0a3ad4d8fa66144fa9905e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logSecurity for shinyreact 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for shinyreact-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.