alanshaw/david-www

Add support for bower.json

Open

#107 建立於 2014年1月21日

在 GitHub 查看
 (10 留言) (1 反應) (0 負責人)JavaScript (733 star) (177 fork)batch import
help wanted

描述

I think these days bower.json is as much important as package.json and so it would totally make sense to provide status reports for bower dependencies. We probably could re-use the same status icon sliced in half for bower and npm based on whether both are in use or only one.

貢獻者指南

技術棧
javascriptnodejs
領域
backendfull stack
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic Node.js knowledgeUnderstanding of npm and bower
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue requests adding support for bower.json, similar to existing package.json handling. The suggestion to reuse the status icon sliced in half for both bower and npm based on usage provides a concrete starting point. Investigate how dependencies are currently fetched and displayed, and implement bower.json parsing following the same pattern. Check for any differences in bower.json format and ensure the code handles cases where only one or both files are present.