Skip to content

Comments

Update templates for nuxt.new #492#1774

Open
maximepvrt wants to merge 4 commits intonuxt:templatesfrom
maximepvrt:update-template
Open

Update templates for nuxt.new #492#1774
maximepvrt wants to merge 4 commits intonuxt:templatesfrom
maximepvrt:update-template

Conversation

@maximepvrt
Copy link

🔗 Linked issue

nuxt/nuxt.new#492

❓ Type of change

  • 📖 Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

@maximepvrt maximepvrt requested a review from danielroe as a code owner February 8, 2026 17:40
@coderabbitai
Copy link

coderabbitai bot commented Feb 8, 2026

📝 Walkthrough

Walkthrough

This change updates 13 template JSON manifest files with standardized metadata fields. Most templates receive three new fields: deprecated, repo, and branch with repository references. Additionally, four templates (content, minimal, module, ui) update descriptive fields including name, description, and/or image. Trailing commas are added to the tar field to accommodate the new properties.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: updating templates for the nuxt.new project (referenced as #492). It is specific enough to indicate the primary modification across multiple template files.
Description check ✅ Passed The description is related to the changeset through the linked issue reference (nuxt/nuxt.new#492), though it lacks detailed explanation of what was changed and why. This is acceptable since the check is lenient and only requires some relation to the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant