- Fixes a 404 on initial app open for SvelteKit projects by adding a
reroutehook that maps/index.htmlto/, correcting the mismatch between Electrobun's load URL and SvelteKit's client-side router.
- Renames the compact agent reference from
docs/llm.txttodocs/llms.txtand updates documentation links.
- Removes the completed V1 release plan document from the published docs.
- Refreshes the README with the current generated stack surface, common recipes, generated commands, and key generated files.
- Improves the post-create final screen with clearer next steps, verification commands, generated file pointers, and add-command guidance.
- Adds
--frontend svelteand--frontend sveltekitrenderer modes with prompts, CLI help, manifest/schema support, generated templates, and validation coverage. - Adds
--packaging installersfor generated AppImage, deb, DMG collection, and NSIS packaging helpers around Electrobun release artifacts.
- Adds a
--frontend preactrenderer mode for smaller direct-rendered WebViews. - Adds
--database json-filefor lightweight local persistence throughdata/app-db.json. - Expands
--native-utilswithclipboardanddesktop-kitoptions backed by Electrobun clipboard utilities. - Adds
--testing desktop-smoke, which includes Bun tests plus a mocked Electrobun main-window launch smoke test.
- Extends generated manifests and schema with Preact, JSON database, clipboard, and desktop smoke-test feature flags.
- Expands generated-project validation to cover Preact, JSON-file persistence, desktop-kit native utilities, and desktop smoke tests.
- Marks the V1 CLI contract as stable after the published
1.0.0-rc.5passed npmnextsmoke tests withnpm create,npx, andbunx --bun. - Ships the documented Electrobun stack generator with the V1 option matrix, manifest compatibility policy, generated-project validation, package smoke tests, and trusted npm publishing workflow.
- Promotes manifest examples and schema URLs from the prerelease package to
1.0.0.
0.xgenerated projects should keep their checked-inces.jsonfile. Future additive features should be applied withcreate-electrobun-stack addwhere possible.standardandfullremain accepted template profile names for compatibility, but they intentionally share the V1minimaltemplate source until they have distinct, tested behavior.- The V1 manifest contract is additive. Breaking manifest migrations require a documented migration path before release.
- Refreshes the V1 release candidate after aligning package repository metadata with npm trusted publishing requirements.
- Updates the generated manifest examples for the new prerelease version.
- Refreshes the V1 release candidate from the npm trusted publishing workflow that uses GitHub Actions OIDC instead of npm token secrets.
- Updates the generated manifest examples for the new prerelease version.
- Refreshes the V1 release candidate from the corrected publish workflow so prerelease publishes resolve to the npm
nextdist-tag by default. - Keeps the generated manifest examples aligned with the next prerelease version.
- Refreshes the release candidate after completing the V1 public-contract, validation, publishing dry-run, and documentation phases.
- Keeps the package behavior aligned with the pre-RC documentation pass and current
main.
- Added a V1 release plan covering public CLI contract, generated project validation, package smoke testing, release candidates, and final
1.0.0gates. - Added generated-project validation scripts for the representative V1 option matrix.
- Added a packed-package smoke test that packs the npm tarball, installs it into a temp consumer project, checks
--version, runs--dry-run, and scaffolds a real app without dependency installation. - Added release workflow gates for generated-project validation and packed-package smoke testing.
- Documented manifest compatibility policy and V1 support boundaries.
0.xgenerated projects should keep their checked-inces.jsonfile. Future additive features should be applied withcreate-electrobun-stack addwhere possible.standardandfullremain accepted template profile names for compatibility, but they intentionally share the V1minimaltemplate source until they have distinct, tested behavior.- The V1 manifest contract is additive. Breaking manifest migrations require a documented migration path before release.