Bug 9231 - npm fetcher registry handling is faulty
Summary: npm fetcher registry handling is faulty
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.1 M4
Assignee: Brendan Le Foll
QA Contact: Francisco Pedraza
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-03-09 05:01 UTC by Paul Eggleton
Modified: 2016-04-18 19:29 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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,