Use Bun Not Npm

For all JS/TS package management and test running in this repo (grasshopper, client, octopus-website, mocky-balboa, octopus-docs), use bun -- never npm.

Source memory file: feedback_use_bun_not_npm.md · Category: Feedback / working-preference This is a verbatim dump of Claude's persistent memory for the Octopus project. Rendered inside a code block so nothing is altered.

---
name: use-bun-not-npm
description: "For all JS/TS package management and test running in this repo (grasshopper, client, octopus-website, mocky-balboa, octopus-docs), use bun -- never npm."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 4a756616-78f2-4e8f-a906-fd34e36a1824
---

For every Node/TS surface in this repo, use **bun** for install, scripts,
and test running. Never invoke `npm` (no `npm install`, no `npm test`, no
`npm run <script>`).

Examples:

- `bun install` (not `npm install`)
- `bun run test` or `bun test` (not `npm test`)
- `bun run dev` (not `npm run dev`)
- `bun add -D <pkg>` (not `npm install --save-dev <pkg>`)
- `bunx <cmd>` (not `npx <cmd>`)

**Why:** User runs bun across the repo and asked explicitly to never use
npm. The `package.json` scripts may still be written with `npm run` in
them historically; invoke them via `bun run <script>` anyway.

**How to apply:** Any time you're about to run a Node-side command in any
of these directories, swap `npm` for `bun`:

- `frontend/grasshopper/`
- `frontend/client/`
- `frontend/octopus-website/`
- `frontend/octopus-docs/`
- `frontend/mocky-balboa/`

When writing new README/test docs in those dirs, use bun commands in
examples too -- don't paste `npm install` snippets into freshly-authored
docs even if existing docs still show them.