Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

npm install --link does not work with git:// dependency URLs #2556

Closed
per-gron opened this Issue Jun 22, 2012 · 4 comments

Comments

Projects
None yet
5 participants

Steps to reproduce

  • Create a new directory and add this package.json file to it:

    { "name": "npm-test2", "version": "1.0.0", "dependencies": { "npm-test": "git://github.com/pereckerdal/npm-test.git" } }

  • In that directory, invoke npm install --link

Expected result

The npm-test package should be installed.

Actual result

npm spits out an error 404 'npm-test' is not in the npm registry.

Additional notes

Invoking npm install, without the --link flag, works as expected.

The same problem exists for git+ssh:// URLs

Here's a gist with npm-debug.log and npm output: https://gist.github.com/2972216

Note: The gist is from an old version of npm, but version 1.1.31 exhibits the same problem.

Contributor

ralt commented Mar 23, 2013

I can confirm the problem still exists.

Here is the gist with a more recent version: https://gist.github.com/Ralt/5228406

@iarna iarna added the bug label Oct 17, 2014

@smikes smikes added a commit to smikes/npm that referenced this issue Dec 20, 2014

@smikes smikes attempt at failing test for #2556 c60f911

@smikes smikes added a commit to smikes/npm that referenced this issue Mar 2, 2015

@smikes smikes attempt at failing test for #2556 abe6a94

@smikes smikes added a commit to smikes/npm that referenced this issue Mar 3, 2015

@smikes smikes attempt at failing test for #2556
working (usually) test case
7baa1f7

@smikes smikes added a commit to smikes/npm that referenced this issue Mar 3, 2015

@smikes smikes attempt at failing test for #2556
make test more reliable
2cf86f4

I also have the same issue. Trying to import a private gist file npm install git+ssh://gist@github.com:#######.git

Collaborator

npm-robot commented Jun 19, 2017

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Jun 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment