Embeddable scene editor, frameos-wasm package, and wasm live preview#260
Merged
Conversation
Split out of #257. The embedded scene editor and in-browser scene runtime: - Embeddable AGPL scene editor bundle published as the frameos-editor npm package: full scene workspace panels, theme support via init message, light-mode diagram styling, hashed entry files, and a demo page; standalone embeds answer API calls with synthetic 404s - frameos-wasm npm package (moved to frameos/wasm): typed wrapper around the emscripten wasm preview worker with a showIf-aware management interface; preview HTTP goes client-side first so the same-origin proxy only carries CORS-blocked hosts - Live preview: renders keep unapplied form edits, one action row, "Save screenshot" in the Preview panel, event buttons send their label in the payload - Release plumbing: publish-npm workflow job, per-package version sync in tools/update_versions.py (editor gets its own component hash in versions.json), pnpm workspace + Dockerfile entries - Auth-guard redirects use replace instead of push so Back does not loop through the redirect The regenerated frontend/src/generated/builtinApps.ts snapshot includes app data from sibling PRs split out of #257 (bird journal app, gallery error-image change); `pnpm --dir frontend run build` regenerates it from the checked-out sources. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
# Conflicts: # AGENTS.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Split out of #257 (FrameOS Cloud link). The embedded scene editor and in-browser scene runtime:
frameos-editor npm package
frameos/editor): serve it from any host, embed in an iframe, exchange scenes JSON over postMessagereplaceinstead ofpushso Back does not loopframeos-wasm npm package
frameos/wasm: typed wrapper around the emscripten wasm preview worker with a showIf-aware management interface (fields, event buttons, logs)Live preview polish
Release plumbing
publish-npmworkflow job (builds the wasm runtime with nim + emsdk, skips when the version exists on npm)tools/update_versions.py; the editor gets its own component hash inversions.jsonNote: the committed
frontend/src/generated/builtinApps.tssnapshot embeds app sources that include changes from sibling PRs split out of #257 (#258's gallery error-image change). Once all siblings merge, the snapshot is exactly fresh;pnpm --dir frontend run buildregenerates it from checked-out sources at any time.Test plan
pnpm --dir frontend run build— builds both the main frontend and the embedded editor bundlepnpm --dir frameos/editor run test— embed API tests passpnpm --dir frameos/wasm run typecheck— passes🤖 Generated with Claude Code