Add bugs.url package metadata

[wangedmund77-cmyk]

Summary

• adds missing npm support/discovery metadata for @tanstack/devtools-vite
• updates only packages/devtools-vite/package.json

Metadata added

• bugs.url: https://github.com/TanStack/devtools/issues

Validation

• parsed packages/devtools-vite/package.json as JSON after the change
• confirmed the changed manifest still has name: @tanstack/devtools-vite
• checked this is metadata-only: no runtime code, dependencies, exports, generated assets, or build behavior changed

This small metadata fix makes the published npm package point users to the project README and/or public issue tracker once the package is next released.

Summary by CodeRabbit

• Chores
  • Updated package metadata to include bug reporting information.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 57b419a9-7b3b-4024-b507-e17bf14085a0

📥 Commits

Reviewing files that changed from the base of the PR and between cf89dcd and cc5f8fe.

📒 Files selected for processing (1)

• packages/devtools-vite/package.json

---

📝 Walkthrough

Walkthrough

The bugs field was added to packages/devtools-vite/package.json to specify the GitHub issues URL where users can report package-related bugs. This updates the package metadata without affecting dependencies, scripts, or exports.

Changes

Package Metadata

Layer / File(s)	Summary
Bugs field addition packages/devtools-vite/package.json	The bugs object with a GitHub issues URL is added to the package manifest for bug reporting reference.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A little field for bugs so grand,
Now users know where issues stand,
To GitHub's issues, they will roam—
The devtools-vite has found a home! 🔗

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides a clear summary of changes and validation performed. However, it does not include the required checklist items from the template (Contributing guide confirmation and test execution).	Complete the checklist section by confirming you followed the Contributing guide and ran pnpm test:pr, or clarify if this is docs/CI/dev-only work.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add bugs.url package metadata' is concise, clear, and directly describes the main change in the PR: adding the bugs.url field to package.json metadata.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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