Read docs/pake-grade-goal.md first. It explains the product bar behind appbun's roadmap.
bun install
bun run build
node ./bin/appbun.js doctor
bun run check
bun run testUseful contribution areas:
- icon extraction quality
- generated shell polish
- Windows and Linux packaging
- generated app ergonomics
- built-in recipes for popular web apps
- docs, examples, and onboarding
Built-in recipes live in src/lib/recipes.ts. Keep them boring and reliable:
- use public URLs that are stable over time
- prefer apps people already recognize
- include a useful
themeColor, and only settitlebar,width, orheightwhen the default is not a good fit - add an alias only when people naturally type it, such as
ytmusicforyoutube-music - add
conceptsthat help people discover the recipe withappbun discover, such asai,design,docs,music, orwork
- keep changes focused
- run
bun run check - run
bun run test - update docs if behavior changes
- prefer improving generated output over adding flags unless the behavior truly needs to vary
appbun should feel closer to a productized generator than a thin script.
That means:
- generated apps should look intentional
- defaults should be clean enough to ship
- packaging flows should reduce manual work
- README and examples should help new contributors move fast