feat(ui): display all engines in Compatibility section and make common ones pretty#1004
Conversation
…n ones pretty This PR makes Compatibility section more generic, making it display any engine that is actually set in packument. On top of that, it makes the list prettier by not displaying raw machine-oriented data but icons and labels for most popular engines.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
📝 WalkthroughWalkthroughThe Compatibility.vue component's 🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
This PR enhances the Compatibility section to display all engine requirements from package.json (not just node and npm), and adds icons and friendly labels for common engines (bun, node, npm).
Changes:
- Changed the
enginesprop type from a specific interface withnode?andnpm?to a genericRecord<string, string>to support any engine - Added mapping objects for engine names and icons with fallbacks for unknown engines
- Replaced hardcoded node/npm display with a dynamic v-for loop that renders all engines
- Added icons to each engine entry for better visual presentation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This PR makes Compatibility section more generic, making it display any engine that is actually set in packument. On top of that, it makes the list prettier by not displaying raw machine-oriented data but icons and labels for most popular engines.
Before (1):
https://npmx.dev/package/rollup
After (1):
Before (2):
(nothing to display)
https://npmx.dev/package/react-jsx-parser
After (2):