Nuxt is a community project - we love contributions of all kinds!

For the complete contribution guides, see:

• General Contribution Guide
• Framework Contribution Guide

1. Fork the nuxt/nuxt repository and clone it locally.
2. Ensure you are using the latest Node.js.
3. Enable Corepack: corepack enable
4. Install dependencies: pnpm install --frozen-lockfile
5. Prepare the development environment: pnpm dev:prepare
6. Create a branch: git checkout -b my-new-branch

• packages/kit - Toolkit for authoring Nuxt modules (@nuxt/kit)
• packages/nuxt - The core of Nuxt (nuxt)
• packages/schema - Cross-version Nuxt typedefs and defaults (@nuxt/schema)
• packages/rspack - The Rspack bundler (@nuxt/rspack-builder)
• packages/vite - The Vite bundler (@nuxt/vite-builder)
• packages/webpack - The webpack bundler (@nuxt/webpack-builder)

• Bug fixes: Check whether there's an existing issue describing the bug.
• Features: Open a feature request issue first to discuss with maintainers. The issue should be confirmed by a team member before building out a feature in a PR.
• Typos: Batch multiple typo fixes into one PR.

We use Conventional Commits. Use fix: and feat: for code changes. Use docs: or chore: for documentation and typo changes. Scope monorepo commits: feat(kit): add utility.

pnpm dev        # Run the playground
pnpm test       # Run tests
pnpm lint       # Check linting
pnpm lint --fix # Auto-fix lint issues

We welcome the thoughtful use of AI tools when contributing to Nuxt, but ask all contributors to follow two core principles:

1. Never let an LLM speak for you - all comments, issues, and PR descriptions should be written in your own words, reflecting your own understanding.
2. Never let an LLM think for you - only submit contributions you fully understand and can explain.

See the full policy.