update-packages
Update Packages
Use this workflow when updating dependencies in this repo.
Steps
- Check the pinned package list in
.ncurc.cjs. Do not upgrade packages listed there. - Keep the repo on Node 24. If you change Node runtime settings, update
.nvmrc,engines.node,@types/node, Dockerfiles, and CI together. - Update manifests across the workspace:
pnpm dlx npm-check-updates -u -ws
- Refresh the lockfile and install updated packages:
pnpm install
- Verify the update:
pnpm test
pnpm lint
Notes
npm-check-updatesreads.ncurc.cjs, so the reject list is applied during the manifest update.pnpm installmay also bump the rootpackageManagerfield and regeneratepnpm-lock.yaml.- Do not run
pnpm devorpnpm buildunless the user explicitly asks. - Keep
@hookform/resolversin the.ncurc.cjsreject list and pinned to4.1.0whileapps/webremains onzod@3.25.76. The5.xresolver line importszod/v4/core, which has caused local Next.js/Turbopack resolution failures even though the app code still uses Zod 3.
More from elie222/inbox-zero
ui-components
UI component and styling guidelines using Shadcn UI, Radix UI, and Tailwind
77security
Security guidelines for API route development
36fullstack-workflow
Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
23test-feature
End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist tests as reusable QA flows or eval files.
21testing
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
21project-structure
Project structure and file organization guidelines
21