skills.rest
dashersw
dasherswCOMMUNITY
Explore all skills by this author →
Website𝕏@dasherswGitHub

playground-browser-bundles

Rebuild gea-core.js and gea-compiler-browser.js bundles in a deterministic build order.

1.2k|46|Updated Mar 18, 2026
Search Tags:#automation#build#sync#playground#vite-plugin#bundles#geajs
One-click install
npx skills add https://github.com/dashersw/gea --skill playground-browser-bundles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playground-browser-bundles
Source: https://github.com/dashersw/gea/tree/main/.cursor/skills/playground-browser-bundles
Command: npx skills add https://github.com/dashersw/gea --skill playground-browser-bundles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep website playground bundles in sync with core and plugin sources to ensure browser bundles stay up to date.

Core Features & Use Cases

  • Rebuild both pre-built bundles: gea-core.js and gea-compiler-browser.js when sources change.
  • Follow the prescribed build order: core dist first, then sync into the playground, then rebuild the browser bundle.
  • Commit conventions: use a dedicated commit for playground bundle updates to keep history clear.

Quick Start

Rebuild the playground bundles by building core, syncing it into the playground, and then building the browser bundle.

Frequently Asked Questions about playground-browser-bundles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep website playground bundles in sync with core and plugin sources?▼

To keep playground bundles in sync, you need a deterministic build order: build the core dist first, sync it into the playground, and then rebuild the browser bundle to ensure consistent previews.

What is the correct build order for rebuilding browser bundles for a playground?▼

The correct build order for browser bundles is to build the core distribution first, then sync that core into the playground directory, and finally rebuild the browser bundle to ensure deterministic and consistent playground previews.

How should I commit changes that update pre-built playground bundles?▼

You should use a dedicated commit specifically for playground bundle updates, which keeps your version history clear and separates bundle generation from core feature development.

Why do my playground previews show outdated code after updating core sources?▼

Playground previews show outdated code because the browser bundles are out of sync, requiring you to follow the prescribed build order to rebuild core, sync the playground, and regenerate the browser bundle.

Do I need to manually rebuild gea-core.js and gea-compiler-browser.js every time sources change?▼

Yes, you need to rebuild both gea-core.js and gea-compiler-browser.js whenever sources change to ensure the browser bundles and playground previews accurately reflect the latest updates.

Related Skills

Explore More Software Engineering Skills→
ElderEvilElderEvil

vite

Migrate Vite 8 projects to Rolldown-based setups with config guidance.

Community
Advanced
krisssskrissss

git-commit

Generate standardized Git commit messages following project conventions and Conventional Commits.

Community
Intermediate
pproencapproenca
193

vite

Optimize Vite application performance through dependency pre-bundling and bundle analysis.

Community
Advanced
realsigridjinrealsigridjin
20

build-fix

Fix TypeScript build and compilation errors with minimal changes.

Community
Intermediate