Skip to content

BUG: don't bomb out if we find a package that isn't in npm #118

Open
@tonywoode

Description

@tonywoode

Describe the bug
I have my own unpublished npm module on my filesystem that I have npm install -g. Making a gist after this has been installed and then trying to do an initial sync fails, and no npm packages at all are installed from the gist:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/replace-slack-text - Not found
npm ERR! 404
npm ERR! 404  '[email protected]' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
...

$ npm list -g --depth=0
/Users/twoode/.nvm/versions/node/v12.18.3/lib
├── [email protected]
└── [email protected]

A couple of other reasons users may have packages not in npm: they might have npm linked them, they might use a private repo in addition to npm...

To Reproduce
Steps to reproduce the behavior:

  1. make a global package that isn't on npm (eg: npm install -g some trivial thing with a package.json)
  2. follow your quickstart instructions to step 3
  3. get the above error, note that no packages from the gist have been installed at this point

Expected behavior
If we can't locate a package on npm, we should continue to print the error, but also try to install all other packages

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions