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

@merna/unhoist

v1.1.2

Published

A merna cli to undo hoisting on a given package-lock.json, reconstructing it using only the root package-lock.json and local packages' package-lock.jsons.

Downloads

12

Readme

@merna/unhoist

A merna cli to undo hoisting on a given package-lock.json, reconstructing it using only the root package-lock.json and local packages' package-lock.jsons.

A tree roughly inspired by npm/arborist (the package used to construct and act on package-lock.json files) is used to update and prune dependencies.

A high level view of the algorithm used:

  • Check for dependencies in the package.json that are not at the top level of the package-lock.json
  • Add all missing remote, top level dependencies to the package-lock.json
  • Add all missing local (to the repo) dependencies using their package-lock.json files recursively unhoisted using the above logic
  • Parse the current temp lockfile into a tree and evaluate every entry in the requires map, adding each to the highest possible level in the tree and checking semver requirements. Each entry is copied from the root package-lock.json. This is naive and results in a ton of duplication.
  • Parse the tree to prune all duplicate dependencies. Every identical dependency in lower levels of the tree that's provided in higher levels is removed
  • Dehydrate the tree into the final lockfile