alanshaw/david-www

Add support for bower.json

Open

#107 opened on Jan 21, 2014

View on GitHub
 (10 comments) (1 reaction) (0 assignees)JavaScript (733 stars) (177 forks)batch import
help wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
backendfull stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic Node.js knowledgeUnderstanding of npm and bower
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.