ermates.blogg.se - Npm update package to specific version

Specify one or more comma-delimited values. Modify the output formatting or show additional information. ncurc.įor the SemVer type definition, see: format Max number of concurrent HTTP requests to registry. (default: 10)įilepath for the cache file. Default -cacheFile is ~/.ncu-cache.json and default -cacheExpiration is 10 minutes.Ĭlear the default cache, or the cache file specified by -cacheFile.Ĭache expiration in minutes. cacheĬache versions to a local cache file. Options that take no arguments can be negated by prefixing them with -no-, e.g. Options are merged with the following precedence:

"Less than" is replaced with a wildcard:.

Range operators are preserved and the version is updated:.

Direct dependencies are updated to the latest stable version:.

Ncu "/^(?!react-).*$/ " # windows How dependency updates are determined Ncu -f "chalk mocha react " # upgrade packages that do not start with "react-".

Ncu "/^react-.*$/ " # upgrade everything except nodemon

replace all the found minimatch folders with the one you just installed in the random locationĪt this point gulp should use the updated minimatch, although npm list will still display the old version number.Īgain, this is highly not recommended and only provided for the sake of answering the question.# upgrade packages that start with "react-".

search for minimatch inside the gulp installation folder ( find.

find your gulp installation folder (this may depend on your system, C:\Users\user\AppData\Roaming\npm\node_modules\gulp on Windows or /usr/lib/node_modules/gulp/ on Linux).

install minimatch somewhere in a random location with npm install go to the node_modules folder in this location and copy the minimatch folder.

If however you really want to perform the operation for whatever reason, you could try the following ugly hack:

Or use the latest version of minimatch directly, using npm install minimatch Update to a new gulp version without worrying about minimatch npm update gulp Let's say your introduces some new features, now might stop working, and in turn might stop working as well. Node modules are designed to contain all dependencies with specified versions inside the node_modules, in order to avoid problems with new updates. You can't and you shouldn't update subpackages (packages used as dependencies for other packages).