chore: replace latest ranges with caret ranges

[danielroe]

🔗 Linked issue

📚 Description

latest is a curse and can easily drift, or change wildly on lockfile regeneration

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/module-builder@782

commit: ba50a65

[coderabbitai]

📝 Walkthrough

Walkthrough

The playground package changes its nuxt dependency from latest to ^4.5.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes replacing the latest dependency range with a caret range.
Description check	✅ Passed	The description explains why replacing latest prevents dependency versions from drifting during lockfile regeneration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch no-latest-ranges

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@example/playground/package.json`:
- Line 9: Align the Nuxt dependency range in the playground manifest with the
lockfile: update the "nuxt" entry to ~4.5.1 for patch-level updates, or retain
^4.5.1 only after regenerating pnpm-lock.yaml so its importer specifier matches.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7565e061-1ec1-4dd3-bfa0-fb9c3658ddf4

📥 Commits

Reviewing files that changed from the base of the PR and between 7490a9e and ba50a65.

📒 Files selected for processing (1)

• example/playground/package.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -A12 -B3 'nuxt|specifier' example/playground/package.json pnpm-lock.yaml

Repository: nuxt/module-builder

Length of output: 50375

---

Align the manifest range with the lockfile range.

example/playground/package.json:9 uses ^4.5.1, while pnpm-lock.yaml records the playground Nuxt importer as specifier: ~4.5.1. If the caret range is intentional, regenerate the lockfile; if only patch-level updates are intended, change the manifest to ~4.5.1.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@example/playground/package.json` at line 9, Align the Nuxt dependency range
in the playground manifest with the lockfile: update the "nuxt" entry to ~4.5.1
for patch-level updates, or retain ^4.5.1 only after regenerating pnpm-lock.yaml
so its importer specifier matches.