chore(docs): update nuxt-component-meta to preview build

[hendrikheil]

Note

This PR is primarily meant for performance review at this stage — not yet ready to merge.

Summary

• Updates nuxt-component-meta in docs/package.json to use the preview build at https://pkg.pr.new/nuxt-component-meta@ef01cc7
• Updates pnpm-lock.yaml accordingly

Test plan

• Verify docs build works with the preview version of nuxt-component-meta

🤖 Generated with Claude Code

[coderabbitai]

📝 Walkthrough

Walkthrough

The docs/package.json file is updated to pin the nuxt-component-meta dependency to a specific build version sourced from pkg.pr.new. The dependency constraint changes from the semver range ^0.17.2 to the pinned version https://pkg.pr.new/nuxt-component-meta@ef01cc7, replacing the npm registry source with a direct URL to a preview build.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating nuxt-component-meta to a preview build in the docs package.
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.
Description check	✅ Passed	The PR description clearly describes the changes made to the repository, explaining the update to nuxt-component-meta and corresponding lock file modifications.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

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 and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/package.json (1)

46-46: ⚡ Quick win

Avoid long-lived preview URL dependency without an explicit rollback check.

Line 46 pins nuxt-component-meta to a pkg.pr.new preview artifact, which is fine for short-term validation but is risky for reproducibility/supply-chain if it lingers. Please add a follow-up guard (or tracking issue) to revert to a registry release before merge/release.

#!/bin/bash
# Verify the lockfile is pinned to the same preview artifact with integrity metadata.
# Expected:
# 1) pnpm-lock.yaml contains ef01cc7 reference for nuxt-component-meta
# 2) lock entry includes integrity/resolution fields
rg -n -C3 'nuxt-component-meta|ef01cc7|pkg\.pr\.new|integrity|resolution' pnpm-lock.yaml

🤖 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 `@docs/package.json` at line 46, The docs/package.json dependency for
nuxt-component-meta is pinned to a pkg.pr.new preview artifact and needs an
explicit rollback plan before merge/release. Update the package metadata around
the nuxt-component-meta entry to add a follow-up guard such as a tracking issue,
TODO, or release gate that ensures this preview URL is reverted to a registry
release, and verify the corresponding pnpm-lock.yaml entry for
nuxt-component-meta remains aligned with the same preview reference and includes
integrity/resolution metadata.

🤖 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.

Nitpick comments:
In `@docs/package.json`:
- Line 46: The docs/package.json dependency for nuxt-component-meta is pinned to
a pkg.pr.new preview artifact and needs an explicit rollback plan before
merge/release. Update the package metadata around the nuxt-component-meta entry
to add a follow-up guard such as a tracking issue, TODO, or release gate that
ensures this preview URL is reverted to a registry release, and verify the
corresponding pnpm-lock.yaml entry for nuxt-component-meta remains aligned with
the same preview reference and includes integrity/resolution metadata.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5b836285-49d6-4f21-b249-a54bf467d48e

📥 Commits

Reviewing files that changed from the base of the PR and between ad7b54e and faf4fee.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• docs/package.json

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@6544

commit: 6fc5ecc