npm / cli
90%
latest: 97%

LAST BUILD BRANCH: nlf/arborist-validation
DEFAULT BRANCH: latest
Repo Added
Files 127
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH isaacs/config-set-multi
branch: isaacs/config-set-multi
CHANGE BRANCH
x

Relevant lines Covered
5151 RELEVANT LINES 4678 COVERED LINES
16.3 HITS PER LINE
Source Files on isaacs/config-set-multi

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
#926 isaacs/config-set-multi Support multiple set/get/deletes in npm config While digging into #2300, I realized it would be a lot easier if we could do this: npm config set email=me@example.com _auth=xxxx and avoid the whole issue of what gets set first. Also, why no... push isaacs pending completion  
#886 isaacs/config-set-multi Support multiple set/get/deletes in npm config While digging into #2300, I realized it would be a lot easier if we could do this: npm config set email=me@example.com _auth=xxxx and avoid the whole issue of what gets set first. Also, why no... push isaacs pending completion  
#884 isaacs/config-set-multi Support multiple set/get/deletes in npm config While digging into #2300, I realized it would be a lot easier if we could do this: npm config set email=me@example.com _auth=xxxx and avoid the whole issue of what gets set first. Also, why no... push isaacs pending completion  
#882 isaacs/config-set-multi Support multiple set/get/deletes in npm config While digging into #2300, I realized it would be a lot easier if we could do this: npm config set email=me@example.com _auth=xxxx and avoid the whole issue of what gets set first. Also, why no... push isaacs pending completion  
See All Builds (3959)