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

package-lock

v1.0.5

Published

(Re-)Build package-lock.json or npm-shrinkwrap.json file from node_modules folder

Downloads

3,082

Readme

package-lock

(Re-)Build package-lock.json or npm-shrinkwrap.json file from node_modules folder

npm@5 Creating package-lock.json

Copying node_modules folders and trying to install additional packages leads to a complete removal of all copied packages with npm@>=5.0.

A package.json file would solve this issue but nonetheless you would need to create one with all it's dependencies.

Running package-lock on the folder which contains node_modules creates the missing package-lock.json file and in case the package.json is missing, it will be created as well. With this you are now save to install additional packages with npm i ...

npm@4, npm@3 Creating npm-shrinkwrap.json

For npm@<=4.x you can also use this package to create a npm-shrinkwrap.json file for fixing you dependencies. For me running npm shrink is mostly a mess as there is always an extraneous dependency showing up (especially after a dedup).

  1. Make a fresh install with
    rimraf node_modules npm-shrinkwrap.json
    npm i --production
  2. Now create the npm-shrinkwrap.json file with
    package-lock -s

Installation

Requires nodejs.

$ npm install -g package-lock

Usage

$ package-lock
Usage: package-lock [options]

Options:

  -p, --package           force appending found packages to `optionalDependencies` in package.json
  -r, --resolve <string>  replace resolved repository
  -s, --shrink            write `npm-shrinkwrap.json` instead of `package-lock.json`
  -h, --help              output usage information

Tests

$ npm test

License

Unlicense http://unlicense.org