shinyreact 0.1.0__tar.gz

shinyreact-0.1.0/.gitignore

@@ -0,0 +1,230 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+!pkg-js/dist/
+pkg-js/dist-npm/
+downloads/
+eggs/
+.eggs/
+lib/
+!pkg-r/inst/lib/
+!examples/*/src/lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer,
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Playwright MCP
+.playwright-mcp/
+
+# Playwright e2e test artifacts (traces, screenshots, videos, HTML report)
+test-results/
+playwright-report/
+.playwright/
+
+# Claude Code local lock files
+.claude/*.lock
+
+# Node
+node_modules/
+
+# Built assets in shiny-react upstream examples
+examples/shiny-react-upstream/*/www/
+shinyui-prototype.png

shinyreact-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Posit Software, PBC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

shinyreact-0.1.0/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.5
+Name: shinyreact
+Version: 0.1.0
+Summary: Shiny UI infrastructure for React-based component rendering
+Project-URL: Homepage, https://posit-dev.github.io/shinyreact/py/
+Project-URL: Documentation, https://posit-dev.github.io/shinyreact/py/
+Project-URL: Repository, https://github.com/posit-dev/shinyreact
+Project-URL: Changelog, https://github.com/posit-dev/shinyreact/blob/main/pkg-py/CHANGELOG.md
+Project-URL: Issues, https://github.com/posit-dev/shinyreact/issues
+Author-email: Barret Schloerke <barret@posit.co>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: dashboard,react,shiny,web
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
+Requires-Python: >=3.10
+Requires-Dist: htmltools>=0.7.0
+Requires-Dist: shiny>=1.8.0
+Description-Content-Type: text/markdown
+
+# shinyreact <a href="https://posit-dev.github.io/shinyreact/"><img src="https://raw.githubusercontent.com/posit-dev/shinyreact/main/pkg-py/docs/logo.svg" align="right" height="138" alt="shinyreact website" /></a>
+
+<!-- badges: start -->
+[![check-py](https://github.com/posit-dev/shinyreact/actions/workflows/check-py.yaml/badge.svg)](https://github.com/posit-dev/shinyreact/actions/workflows/check-py.yaml)
+<!-- badges: end -->
+
+shinyreact lets you write the UI of a [Shiny for Python](https://shiny.posit.co/py/) app as a [React](https://react.dev/) 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](https://posit-dev.github.io/shinyreact/js/) backs the [R package](https://posit-dev.github.io/shinyreact/r/), so one React client works against an `app.py` or an `app.R` server. The [full site](https://posit-dev.github.io/shinyreact/) covers all three.
+
+## Installation
+
+```bash
+pip install shinyreact
+```
+
+Or install the development version from GitHub:
+
+```bash
+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:
+
+```python
+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:
+
+```python
+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`:
+
+```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:
+
+```bash
+git clone https://github.com/posit-dev/shinyreact
+shiny run shinyreact/examples/01-hello/app.py
+```
+
+## Learn more
+
+- [Get started](https://posit-dev.github.io/shinyreact/) walks through the `ui.tsx` pattern: inputs, outputs, messages, and embedding traditional Shiny renderers.
+- [TSX files and JavaScript build tools](https://posit-dev.github.io/shinyreact/articles/tsx-and-build-tools.html) explains `.tsx`, JSX, TypeScript, and what `npm run build` does.
+- [Client hooks](https://posit-dev.github.io/shinyreact/articles/hooks.html) lists everything at `window.shinyreact`.
+- [Testing](https://posit-dev.github.io/shinyreact/articles/testing.html) covers shiny's `local_server` pytest fixture for driving a server with no browser, and `WireTap` for wire payloads in Playwright tests.
+- [Agent Skills](https://posit-dev.github.io/shinyreact/articles/agent-skills.html) explains the skills that ship with the package for coding agents.
+- The [examples catalog](https://github.com/posit-dev/shinyreact/blob/main/examples/README.md) lists runnable apps from no-build to Vite + HMR.

shinyreact-0.1.0/pkg-py/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog
+
+## 0.1.0
+
+* Initial PyPI release.
+
+* Server-side plumbing for the `ui.tsx` pattern: the UI is a React client you
+  own, and the Shiny server contains only reactive computation.
+  `@reactive_output` sends JSON to `useShinyOutputValue()` hooks,
+  `send_message()` reaches `useShinyMessageHandler()`, and `set_react_page()`
+  (Express), `ReactApp` (Core), `page_react()`, `page_react_html()`,
+  `page_bare()`, and `page_react_dep()` bootstrap the client.
+
+* Renderer dependencies of traditional Shiny outputs hosted inside a React tree
+  are discovered automatically, so `ShinyOutput` works with zero configuration.
+
+* Bookmark restore is delivered through the `#shinyreact-config` script tag,
+  and the client asserts the wire-protocol major version at boot.
+
+* `shinyreact.default` and `shinyreact.asis` input handlers give Python and R
+  the same view of the JSON a hook sends.
+
+* `shinyreact.playwright.WireTap` records the Shiny websocket for end-to-end
+  tests.

shinyreact-0.1.0/pkg-py/README.md

@@ -0,0 +1,87 @@
+# shinyreact <a href="https://posit-dev.github.io/shinyreact/"><img src="https://raw.githubusercontent.com/posit-dev/shinyreact/main/pkg-py/docs/logo.svg" align="right" height="138" alt="shinyreact website" /></a>
+
+<!-- badges: start -->
+[![check-py](https://github.com/posit-dev/shinyreact/actions/workflows/check-py.yaml/badge.svg)](https://github.com/posit-dev/shinyreact/actions/workflows/check-py.yaml)
+<!-- badges: end -->
+
+shinyreact lets you write the UI of a [Shiny for Python](https://shiny.posit.co/py/) app as a [React](https://react.dev/) 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](https://posit-dev.github.io/shinyreact/js/) backs the [R package](https://posit-dev.github.io/shinyreact/r/), so one React client works against an `app.py` or an `app.R` server. The [full site](https://posit-dev.github.io/shinyreact/) covers all three.
+
+## Installation
+
+```bash
+pip install shinyreact
+```
+
+Or install the development version from GitHub:
+
+```bash
+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:
+
+```python
+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:
+
+```python
+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`:
+
+```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:
+
+```bash
+git clone https://github.com/posit-dev/shinyreact
+shiny run shinyreact/examples/01-hello/app.py
+```
+
+## Learn more
+
+- [Get started](https://posit-dev.github.io/shinyreact/) walks through the `ui.tsx` pattern: inputs, outputs, messages, and embedding traditional Shiny renderers.
+- [TSX files and JavaScript build tools](https://posit-dev.github.io/shinyreact/articles/tsx-and-build-tools.html) explains `.tsx`, JSX, TypeScript, and what `npm run build` does.
+- [Client hooks](https://posit-dev.github.io/shinyreact/articles/hooks.html) lists everything at `window.shinyreact`.
+- [Testing](https://posit-dev.github.io/shinyreact/articles/testing.html) covers shiny's `local_server` pytest fixture for driving a server with no browser, and `WireTap` for wire payloads in Playwright tests.
+- [Agent Skills](https://posit-dev.github.io/shinyreact/articles/agent-skills.html) explains the skills that ship with the package for coding agents.
+- The [examples catalog](https://github.com/posit-dev/shinyreact/blob/main/examples/README.md) lists runnable apps from no-build to Vite + HMR.