Skip to content

Add installed project creation and native/web starter commands - #171

Draft
proggeramlug wants to merge 1 commit into
codex/compiled-web-startupfrom
codex/starter-cli
Draft

Add installed project creation and native/web starter commands#171
proggeramlug wants to merge 1 commit into
codex/compiled-web-startupfrom
codex/starter-cli

Conversation

@proggeramlug

@proggeramlug proggeramlug commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

New projects currently require manual compiler commands, native-library permissions and separate web serving steps. Add a packaged bloom command for project creation, host-native build/run, and web build/serve from the same TypeScript template, with an asset example and separate init/update/draw/cleanup functions.

bloom new carries the exact engine package into the project as .bloom/engine.tgz, then installs it. This prevents a draft archive at version 0.4.16 from accidentally selecting the older registry release with the same version. It writes compatible Bloom/Perry metadata and native-library permissions, preserves existing directories, and rejects incompatible projects, missing tools and unsupported targets. Windows can prepare/reuse the existing pinned compiler/runtime helper; web serving binds localhost and uses an asset prefetch manifest.

Local validation: a fresh installed CLI creates a project and builds the unmodified native template (270.360 seconds). Its npm start path builds/runs a bounded copy (10.141 seconds), renders the 800x450 greeting and square, reads the asset and cleans up once on Radeon DX12. Restoring the unmodified source completes the full web build (63.765 seconds). A separate fresh-package check passes default creation without the explicit archive option, verifies installed sources and rejects missing compiler/unsupported target controls. Cached managed toolchain validation also passes.

Five behavioral tests and repository/package/FFI contracts pass. Add required Windows installed-package creation evidence to CI. Native runtime tests use a qualified existing Perry profile, headless rendering and SDK shader DLLs on PATH. Visible native presentation, actual compiled-starter browser rendering, macOS/Linux starter runtime, fresh-machine setup through this CLI, fixed updates, hot reload and distributable shader runtimes remain open. This draft does not release npm 0.5 or close the full starter issue.

Stacked on #170; relates to #142, #74 and #145. Hosted Tests run 34565911332 passes all 22 jobs, including fresh installed default creation and its negative controls. The PR head and hosted checkout have identical Git trees. The minimal compiled-game browser check also passes; full starter browser rendering remains unqualified. The draft usage and validation scope are documented in docs/starter.md and docs/evidence/windows-starter-cli-v1.md.

Published report and evidence retain local native/web builds, default-creation controls, the greeting capture, exact final source and successful hosted results. ZIP SHA-256: 8051a5bb6df184b611fc03b9be94c7f81c664a3e70d9fede12b38ca97a27f678.

@coderabbitai

coderabbitai Bot commented Sep 11, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

1 participant