riyadhalnur / npm-modules-sync Goto Github PK

At the moment, the module will install packages without any constraints, i.e all packages will fall back to the latest tag on npm. The module should respect the version number of packages.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Title self explanatory, the link goes to : https://github.com/riyadhalnur/npm-modules-sync/blob/master/docs/docs.md

Self explanatory.

The dependency update-notifier was updated from 2.5.0 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

• node version: 9.5.1
• npm version: 5.7.1

Error output

 ➜  ~ npm-sync init -t XXX -i XXX     
 ✔ Writing configuration to disk
 ❯ Fetching information from GitHub
   ✔ Get list of packages from GitHub
   ✖ Install npm packages globally
TypeError: Cannot create property 'context' on string 'npm ERR! code ENOLOCAL
npm ERR! Could not install from "" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/fabianhenzler/.npm/_logs/2018-02-27T09_05_06_299Z-debug.log
'
    at tasks.then.catch.err (/usr/local/lib/node_modules/npm-modules-sync/node_modules/listr/index.js:74:17)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)

More details

Command aliases for the main commands - download and upload have not been implemented yet. Minor change but definitely something that would be a welcome feature.

By default, download will install the version that is saved. It would also be useful to override this to install the latest version of a package if needed, i.e download --latest?

Bash completion script would make like easier.

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

When downloading, the package should diff against the saved list on gist with local global packages and remove packages from local as required based on filtered list.

The new version of this modules is using a broken version of husky. Due to changes downstream, husky is failing. But since it's a dev dependency only, it won't affect this module itself. Will need to bump version once a fix is pushed for husky.

The module should fail gracefully with a crafted message to indicate that there are no packages to back up.