Skip to content

chore: release v0.23.0 - #134

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
tegami/version-packages
Open

chore: release v0.23.0#134
github-actions[bot] wants to merge 1 commit into
mainfrom
tegami/version-packages

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary

All bumped packages.

Package From To
@reactunity/renderer 0.22.0 0.23.0
@reactunity/material 0.22.0 0.23.0
@reactunity/create 0.22.0 0.23.0
@reactunity/scripts 0.22.0 0.23.0

Changelogs

2026-07-28-a7f3c1.md

Show Bumped Packages (1)
Package Bump
npm:@reactunity/scripts minor

Serve the web previewer without installing it

The dev server's previewer now works out of the box. Visiting the dev server address in a browser opens a Unity WebGL player running your UI, with no extra package to install.

Previously this required the optional @reactunity/previewer dependency, which shipped a ~107 MB Unity build in its npm tarball — a cost every install paid for a page many projects never opened. The build is now hosted on reactunity.github.io and fetched on first load, then cached by the browser. @reactunity/previewer is no longer used and has been dropped from peerDependencies; you can remove it from your project.

Because the build is fetched rather than bundled, the first load needs network access. To preview offline — or to preview your own Unity scene — put a previewer build in a previewer folder in your project so that previewer/index.html exists. The dev server serves that in preference to the built-in previewer, and your project's own public folder takes precedence over both.

The dev server also serves /info.html, explaining how to point Unity's DevServer property at it. That guidance used to be the page shown at /.

Fix the previewer folder override being ignored

A custom previewer placed in a previewer folder was never actually served. The dev server read paths.appPreviewer, but that key was only defined when developing react-unity-scripts in its own repository — in a published install the path resolved to undefined, so the documented override silently did nothing.

Publish

The following packages will be published if merged:

Package Version Registry
@reactunity/renderer 0.23.0 npm
@reactunity/material 0.23.0 npm
@reactunity/create 0.23.0 npm
@reactunity/scripts 0.23.0 npm

@github-actions
github-actions Bot force-pushed the tegami/version-packages branch from 6bc0797 to 0b2d226 Compare July 27, 2026 22:26
@github-actions
github-actions Bot force-pushed the tegami/version-packages branch from 0b2d226 to 40f85fa Compare July 28, 2026 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants