cannot install component from bitbucket

[frankwallis]

A recent change has broken component installation.

I am running on Windows and everything works using component-remotes 1.1.6, but if I update to component-remotes 1.1.8 then component install fails silently.

[timaschew]

can you run component install with debug please: DEBUG=* component install component/domify

[frankwallis]

the problem seems to be limited to BitBucket repos:

component install jhc-systems/angular --debug

  component-resolver remote not set - defaulting to remotes's defaults +0ms
  component-resolver:locals resolving local at "C:\Work\bitbucket\app" +3ms
  component-resolver resolving "root" +1ms
  component-resolver remaining dependencies: 1 +4ms
  component-resolver remaining semver: 0 +0ms
  component-resolver finished resolving locals +1ms
  component-resolver finished resolving dependencies (1) +1ms
  component-resolver:semver resolving semver jhc-systems/angular@* +1ms
  component-resolver:dependencies resolving dependency jhc-systems/angular@1.3.1 +2s
  component-resolver:dependencies searching ["local","github","bitbucket"] for jhc-systems/angular@1.3.1 +1ms

component/domify works ok:

 component-resolver remote not set - defaulting to remotes's defaults +0ms
  component-resolver:locals resolving local at "C:\Work\bitbucket\app" +3ms
  component-resolver resolving "root" +1ms
  component-resolver remaining dependencies: 1 +4ms
  component-resolver remaining semver: 0 +0ms
  component-resolver finished resolving locals +1ms
  component-resolver finished resolving dependencies (1) +1ms
  component-resolver:semver resolving semver component/domify@* +1ms
  component-resolver:dependencies resolving dependency component/domify@1.3.1 +1s
  component-resolver:dependencies searching ["local","github","bitbucket"] for component/domify@1.3.1 +2ms
  component-resolver:dependencies found component/domify@1.3.1 from remote "github" +3ms
  component-resolver resolving "component/domify" +0ms
  component-resolver remaining dependencies: 0 +1ms
  component-resolver remaining semver: 1 +1ms
  component-resolver:semver resolved semver component/domify@* -> component/domify@1.3.1 +3ms
  component-resolver finished resolving semver +0ms
  component-resolver finished resolving dependencies(2) +1ms
   installed : component/domify@1.3.1 in 220ms
  component-resolver finished installing dependencies +224ms
     install : complete

thanks

[timaschew]

thanks, can confirm the issue, will try to fix it soon.
For now, you can pin your transitive deps (in this case remotes: 1.1.6) via a npmshrinkwrap

[frankwallis]

will do, thanks

[netpoetica]

@timaschew What do you think the issue is here? In the debug output, it looks like it's just hanging up in the search? Something to do with checking version first from this commit: 7b67827#diff-8025693921c2b5a41af819d9f259b7b9R91

[timaschew]

Don't know what is going on here, the tests passed: https://travis-ci.org/componentjs/remotes.js/jobs/41913111

Have no time this week, will investigate the issue next week