Bug 9231

Summary: npm fetcher registry handling is faulty
Product: [Build System, Metadata & Runtime] BitBake Reporter: Paul Eggleton <bluelightning>
Component: bitbakeAssignee: Brendan Le Foll <brendan.le.foll>
Status: RESOLVED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: brendan.le.foll, francisco.j.pedraza.gonzalez, poky.bs.watcher, poky.watcher, richard.purdie
Version: 2.0   
Target Milestone: 2.1 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Paul Eggleton 2016-03-09 05:01:01 UTC 
The npm fetcher attempts to construct a registry URL to pass to --registry, but unfortunately it's not doing this correctly at the moment - ud.basename ends up as '' with the result that ud.registry is 'http://'. npm doesn't seem to care, so I wonder if it's paying any attention to this option at all. Either way we need to fix all of the problems here so that registries other than the main one can actually be used.
Comment 2 Francisco Pedraza 2016-04-18 19:29:06 UTC 
Hi Paul,
Could you please tell me more details in order to be able to reproduce this one?, I need to verify this.
Regards,