bun-first
Describes efficient usage of Bun and Bun APIs instead of Node.js (and its APIs)
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install academind-ai-config-bun-first
Repository
Skill path: skills/bun-first
Describes efficient usage of Bun and Bun APIs instead of Node.js (and its APIs)
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: academind.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install bun-first into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/academind/ai-config before adding bun-first to shared team environments
- Use bun-first for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: bun-first description: Describes efficient usage of Bun and Bun APIs instead of Node.js (and its APIs) --- # Bun-First Development We default to **Bun** as our JavaScript runtime, package manager, and task runner. Assume Bun is available unless explicitly stated otherwise. ## General Principles - **PREFER** Bun over Node.js, npm, pnpm, or yarn - **PREFER** Bun’s built-in features over third-party tools when available - **PRFER** Bun's native APIs (eg for file access, SQL, S3 etc) over Node.js APIs ## Package Management - **USE** `bun install`, `bun add`, `bun remove` - **AVOID** `npm`, `yarn`, `pnpm` - Prefer Bun-native lockfiles and resolution behavior - Keep dependencies minimal and intentional ## Scripts & Tooling - **PREFER** `bun run` for scripts - **AVOID** Bun’s built-in test runner (`bun test`) => We'll use `Vitest` for testing - **AVOID** Bun’s build tool (`bun build`) => We'll use Vite - Avoid introducing extra task runners unless required ## Runtime & APIs - **PREFER** Bun’s native APIs (fetch, fs, path, env handling) - Write code assuming modern Web APIs are available in the runtime - Avoid Node-specific APIs unless explicitly required ## Performance & DX - Prefer simple, explicit scripts over complex toolchains - **AVOID** unnecessary abstractions