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

x-package-version-strict-check

v1.8.0

Published

A tool to check package's version strictly in project.

Downloads

130

Readme

Introduction

This is a tool to check package's version strictly in project.We often encounter an unknown problem when the version of a package in a local environment is different from that in another environment, such as a production environment or another computer environment, resulting in different compiled script code.Therefore, this tool can be used to enforce consistency of package version Numbers across all environments, and hopefully it will be useful to you!

Theory

  • Check the following files in the package version number is exactly the same :./node_modules , ./package-lock.json , ./package.json
  • Check the Node.js version with installed if you set version in package.json via engines.node

Usage

  • Remove fuzzy versions of the characters in package.json , such as ^
  • Add Node.js version in package.json if you want
  • npm install --save-dev x-package-version-strict-check
  • Add script in package.json
  "scripts": {
    "check": "x-package-version-strict-check"
  }
  • npm run check, if have some error, you will see them like this:
> x-package-version-strict-check
Please wait while checking the version information......
Start checking the version number in package.json...
Module jquery: package.json's version(1.3.1) is different with package-lock.json version(3.3.1)!
Module x-package-version-strict-check: package.json's version(1.5.0) is different with package-lock.json version(1.5.1)!
npm ERR! Test failed.  See above for more details.

CLI

  • --path: Specify the project root path which you want to check.