// Rebuild the website playground browser bundles after changing @geajs/core or @geajs/vite-plugin source. Use when building browser bundles, syncing the playground, or committing changes that affect the playground preview.
| name | playground-browser-bundles |
| description | Rebuild the website playground browser bundles after changing @geajs/core or @geajs/vite-plugin source. Use when building browser bundles, syncing the playground, or committing changes that affect the playground preview. |
The website playground at website/playground/ ships two pre-built browser bundles:
| Bundle | Source package | Build command |
|---|---|---|
gea-core.js | @geajs/core | npm run build -w @geajs/core then npm run sync:playground-gea-core |
gea-compiler-browser.js | @geajs/vite-plugin | npm run build:browser -w @geajs/vite-plugin |
Rebuild both bundles whenever either package's source changes. The compiler generates code that calls runtime helpers from core (e.g. geaEscapeHtml, geaSanitizeAttr), so they must stay in sync.
Order matters — gea-core.js is copied from the dist build, so the core package must be built before syncing:
# 1. Rebuild core dist (required if core source changed)
npm run build -w @geajs/core
# 2. Copy built core into playground
npm run sync:playground-gea-core
# 3. Rebuild compiler browser bundle
npm run build:browser -w @geajs/vite-plugin
Bundle rebuilds go in a separate commit: chore: rebuild playground browser bundles.
Use when creating Gea applications, components, stores, routes, SSR entry points, JSX templates, or working with Gea reactivity and DOM patching.
Guide for using @geajs/ui — a Tailwind-styled, Zag.js-powered component library for the Gea framework. Use when building UIs with @geajs/ui components like Button, Select, Dialog, Tabs, Toast, or any pre-built component from the library.
Step-by-step guide for migrating React applications to Gea — covering project setup, component conversion, state management, routing, styling, and known pitfalls. Use when converting an existing React codebase to Gea or when advising on migration strategy.
Rebuild the local js-framework-benchmark HTML report using the curated framework set for this repo, and avoid polluting the report with every framework in webdriver-ts/results. Use when the user asks to update the benchmark report, refresh webdriver-ts-results, regenerate the HTML results page, or compare Gea against vanilla, solid, vue, and react.