You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
make a global package that isn't on npm (eg: npm install -g some trivial thing with a package.json)
follow your quickstart instructions to step 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
The text was updated successfully, but these errors were encountered:
@tonywoode thank you for filing this! would make for a good feature. I do have plans to add a diff and dry-run flag (#97) for safer syncing. Any PR is always welcome. I don't get much time these days and I'm not sure if the usage stats for this helper warrant any more attention from me for the time being.
it seems to me as if you're the only person in the world making a tool that can replicate an install of the heavily-relied-upon modules from the world's largest code repository. I'm amazed at the lack of usage. People are messy and tend to repeat tasks ;-)
I'm not in any position to do a PR right now i'm afraid, would love to otherwise....
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:A couple of other reasons users may have packages not in npm: they might have
npm link
ed them, they might use a private repo in addition to npm...To Reproduce
Steps to reproduce the behavior:
npm install -g
some trivial thing with a package.json)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
The text was updated successfully, but these errors were encountered: