library-version-upgrade

Table of contents

• library-version-upgrade
• Overview
• Install
• Usage
• Limitation
• References
• Author Info

Overview

The aim of the project is to help with if there is a package in the dependency graph of your project and now if you want to update that then how much updations are needed for the direct dependencies of your project

Install

    npm install library-version-upgrade

OR

    yarn add library-version-upgrade

---

Usage

    library-version-upgrade <dependencyName> <requiredVersion> 

OR

    node_modules/.bin/./library-version-upgrade <dependencyName> <requiredVersion> 

OR

    npx library-version-upgrade <dependencyName> <requiredVersion> 

This will provide with a list of all the packages (which are the dependencies of your project and are depended directly or indirectly on dependency) need to be updated and how much you need to update each of these packages , sometimes if all the versions of a package depends on a lower version of dependency then this will be reported.

Note

Peer dependencies and dev dependencies are ignord here so a lower version of dependency can still be present in the lock file.

Yarn@3.x should be installed as the yarn -why command is used

Some packages are not present in the npm registry these are not considered while making dependency graph

---

Limitations

The algorithm here assumes that with an upgrade the versions of the dependency graph changes monotonically, this assumption is wrong very rarely and in this case the output might not be true.

References

• npmjs
• yarn-why
• semver

---

Author Info

Pradeep Singh

• Email- pradeepanddhruv@gmail.com
• Github- psychobot-2

---