chore: add package support metadata

[YfengJ]

Summary

• add the package homepage pointing to the repository README
• add the package bugs URL pointing to the repository issues page

Why

The published npm metadata currently exposes the repository and license, but does not include homepage or bugs fields. Adding these fields makes the package support links easier to discover from npm and package tooling.

Current npm metadata checked with:

npm view rsbuild-plugin-workspace-dev@latest name version repository homepage bugs license --json

{
  "name": "rsbuild-plugin-workspace-dev",
  "version": "1.0.0",
  "repository": "https://github.com/rstackjs/rsbuild-plugin-workspace-dev",
  "license": "MIT"
}

Validation

• node -e "const p=require('./package.json'); if(p.homepage !== 'https://github.com/rstackjs/rsbuild-plugin-workspace-dev#readme') throw new Error('bad homepage'); if(!p.bugs || p.bugs.url !== 'https://github.com/rstackjs/rsbuild-plugin-workspace-dev/issues') throw new Error('bad bugs url'); console.log(JSON.stringify({homepage:p.homepage, bugs:p.bugs}, null, 2));"
• pnpm install --frozen-lockfile --ignore-scripts
• pnpm run lint
• pnpm run build
• pnpm run test:unit
• pnpm run test:e2e
• pnpm run test (exited 0; unit and e2e passed, while the existing e2e app logs TypeScript diagnostics during dev-server startup)
• npm pack --dry-run --ignore-scripts --json .
• git diff --check

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ba6f4512-c9d5-4d5f-8571-6da399b3aa7b

📥 Commits

Reviewing files that changed from the base of the PR and between 1d2e4fe and d1b7dd0.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

The package.json manifest is extended with two new metadata fields: a homepage URL and a bugs object containing a url pointing to the GitHub issues page. No other fields, scripts, or dependencies are modified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: add package support metadata' directly and concisely describes the main change—adding homepage and bugs fields to package.json metadata.
Description check	✅ Passed	The description clearly explains the changes (adding homepage and bugs fields), the rationale (improving npm metadata discoverability), current validation status, and verification steps performed.
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

---

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