Add npm repository metadata#4
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis pull request updates ChangesPackage metadata
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
repositorymetadata pointing to this GitHub repoWhy
The published
@itseasy21/mcp-knowledge-graph@1.0.7package exposeshomepageandbugs, while npm metadata currently omitsrepository. Adding the standard repository field helps npm users and package tooling trace the package back to source directly.Verification
node -e "const p=require('./package.json'); if(!p.repository?.url) process.exit(1); console.log(p.repository.url); console.log(p.bugs);"npm pack --dry-run --ignore-scriptsgit diff --checkThis is a package metadata-only change.
Summary by CodeRabbit