This is similar to npm-check interactive update mode. It provides an easy way to update outdated packages.
upgrade-interactive command takes the same parameters as, and functions the same as the base
This command will display the outdated packages before performing any upgrade, allowing the user to select which packages to upgrade.
Yarn will respect the version ranges in
package.json when determining the version to upgrade to.
You can think of
yarn upgrade-interactive as a combination of the
yarn outdated and
yarn upgrade [package...] commands.
yarn outdated displays the list of outdated packages and
yarn upgrade [package...] can then be used to upgrade desired packages,
yarn upgrade-interactive displays the same outdated package list and lets you immediately chose which to upgrade.
--latest : This flag tells yarn to ignore the specified version ranges in
package.json and instead use the version tagged
in the registry.
[1/? Choose which packages to update. (Press <space> to select, <a> to toggle all, <i> to inverse s election) devDependencies ❯◯ autoprefixer 6.7.7 ❯ 7.0.0 https://github.com/postcss/autoprefixer#readme ◯ webpack 2.4.1 ❯ 2.5.1 https://github.com/webpack/webpack dependencies ◯ bull 2.2.6 ❯ 3.0.0-alpha.3 https://github.com/OptimalBits/bull#readme ◯ fs-extra 3.0.0 ❯ 3.0.1 https://github.com/jprichardson/node-fs-extra ◯ socket.io 1.7.3 ❯ 1.7.4 https://github.com/socketio/socket.io#readme ◯ socket.io-client 1.7.3 ❯ 1.7.4 https://github.com/Automattic/socket.io-client#readme
When you want to use another package, you first need to add it to your dependencies. Running `yarn add` installs it into your project.
Tags are a way of publishing versions of your package with a label. Users of your package can install that instead of a version number.
Versions of dependencies
Packages in Yarn follow Semantic Versioning, also known as “semver”. When you install a new package it will be added with a semver version range.