npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

library-version-upgrade

v2.1.2

Published

provide a package to update and get all the required updates in the package .json file (you must be using Yarn 3.x)

Downloads

11

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

pradeepsingh107pradeepsingh107

Keywords

Readme

library-version-upgrade

Table of contents

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.

[email protected] 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

Author Info

Pradeep Singh