参与 Nuxt 生态建设

# Fork 后克隆 Nuxt 核心仓库
git clone https://github.com/YOUR_NAME/nuxt.git
cd nuxt
 
# 安装依赖（Nuxt 使用 pnpm workspace）
corepack enable
pnpm install
 
# 构建所有包
pnpm build
 
# 运行测试
pnpm test
 
# 启动 playground 进行开发验证
pnpm dev:prepare
pnpm dev

# 1. 创建分支
git checkout -b fix/async-data-key-conflict
 
# 2. 找到相关代码
# Nuxt 核心代码结构：
# packages/nuxt/src/app/composables/asyncData.ts  ← useAsyncData
# packages/nuxt/src/app/composables/fetch.ts       ← useFetch
# packages/nuxt/src/pages/runtime/                 ← 路由相关
# packages/nitro/                                   ← 服务端引擎
 
# 3. 写测试（必须！PR 没有测试不会被合并）
# test/fixtures/ 下添加测试 fixture
# test/ 下添加测试用例
 
# 4. 提交
git commit -m "fix(nuxt): resolve async data key conflict in nested routes"

## Description
Fix async data key conflict when multiple components in nested routes 
use the same key string.
 
## Changes
- Added automatic key scoping based on component path
- Added test case for nested route key conflict
 
## Checklist
- [x] Linked related issue: #12345
- [x] Added tests
- [x] Updated docs (if applicable)
- [x] Ran `pnpm test` locally

# RFC: [Feature Name]
 
## Summary
One paragraph description of the feature.
 
## Motivation
Why are we doing this? What use cases does it support?
 
## Detailed Design
Technical details of the implementation.
 
### API Design
```ts
// How users would use this feature
const result = useNewFeature({ option: 'value' })

// src/module.ts
import { defineNuxtModule, addPlugin, createResolver, addImportsDir } from '@nuxt/kit'
 
export interface ModuleOptions {
  apiKey?: string
  debug?: boolean
}
 
export default defineNuxtModule<ModuleOptions>({
  meta: {
    name: 'my-nuxt-module',
    configKey: 'myModule',
    compatibility: { nuxt: '>=3.0.0' },
  },
  defaults: {
    debug: false,
  },
  setup(options, nuxt) {
    const resolver = createResolver(import.meta.url)
 
    // 1. 注入运行时配置
    nuxt.options.runtimeConfig.public.myModule = {
      apiKey: options.apiKey || '',
      debug: options.debug,
    }
 
    // 2. 自动导入 composables
    addImportsDir(resolver.resolve('./runtime/composables'))
 
    // 3. 注册插件
    addPlugin(resolver.resolve('./runtime/plugin'))
 
    // 4. 添加组件目录
    nuxt.hook('components:dirs', (dirs) => {
      dirs.push({ path: resolver.resolve('./runtime/components') })
    })
 
    // 5. 添加服务端 API 路由
    nuxt.hook('nitro:config', (nitroConfig) => {
      nitroConfig.handlers = nitroConfig.handlers || []
      nitroConfig.handlers.push({
        route: '/api/my-module/health',
        handler: resolver.resolve('./runtime/server/api/health.get'),
      })
    })
  },
})

// src/runtime/composables/useMyModule.ts
export function useMyModule() {
  const config = useRuntimeConfig().public.myModule
 
  async function fetchData(endpoint: string) {
    return $fetch(endpoint, {
      headers: { 'X-API-Key': config.apiKey },
    })
  }
 
  return { fetchData, debug: config.debug }
}

// test/module.test.ts
import { describe, it, expect } from 'vitest'
import { setup, $fetch } from '@nuxt/test-utils'
 
describe('my-nuxt-module', async () => {
  await setup({
    fixture: 'fixtures/basic',
    server: true,
  })
 
  it('renders the component', async () => {
    const html = await $fetch('/')
    expect(html).toContain('my-module')
  })
 
  it('provides composable', async () => {
    const html = await $fetch('/test')
    expect(html).toContain('module-data')
  })
})

// package.json
{
  "name": "my-nuxt-module",
  "version": "1.0.0",
  "type": "module",
  "exports": {
    ".": {
      "types": "./dist/types.d.ts",
      "import": "./dist/module.mjs",
      "require": "./dist/module.cjs"
    }
  },
  "main": "./dist/module.cjs",
  "types": "./dist/types.d.ts",
  "files": ["dist"],
  "keywords": ["nuxt", "nuxt-module"],
  "scripts": {
    "dev": "nuxi dev playground",
    "build": "nuxt-module-build build",
    "test": "vitest",
    "prepublishOnly": "pnpm build"
  }
}

pnpm build
npm publish

入门级：
1. packages/nuxt/src/app/composables/asyncData.ts
   → 理解 useAsyncData 的 SSR 数据获取机制
2. packages/nuxt/src/app/composables/fetch.ts
   → useFetch 是 useAsyncData + $fetch 的封装
3. packages/nuxt/src/app/plugins/router.ts
   → 路由系统如何初始化
 
进阶级：
4. packages/nuxt/src/core/nuxt.ts
   → Nuxt 实例的生命周期和 hook 系统
5. packages/nuxt/src/core/builder.ts
   → 构建流程编排
6. packages/kit/src/module/define.ts
   → defineNuxtModule 的实现
 
高级：
7. packages/nuxt/src/app/entry.ts
   → 客户端 hydration 流程
8. packages/nuxt/src/core/plugins/
   → 构建时如何处理自动导入、页面扫描

# 在 Nuxt 源码中加断点调试
cd nuxt
pnpm dev:prepare
 
# 修改 packages/nuxt/src/app/composables/asyncData.ts
# 添加 console.log 或 debugger
 
# 在 playground 中测试
cd playground
pnpm dev

文章选题建议：
- 迁移经验：「我把 XX 项目从 Nuxt3 迁移到 Nuxt4 的经历」
- 踩坑记录：「Nuxt SSR Hydration Mismatch 的 5 种场景」
- 模块开发：「我开发了一个 Nuxt Module，解决了 XX 问题」
- 性能优化：「Nuxt4 项目 Lighthouse 从 60 分到 95 分」
- 源码解读：「useAsyncData 源码深度解析」