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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hwbdev/nested-package

v1.0.2

Published

This package is used to test where and how npm installs packages when the package themself have other dependencies.

Readme

This package is used to test where and how npm installs packages when the package themself have other dependencies.

npm will try to install any packages in the top-most level node_modules folder. However, if that can't be done because two packages have the same dependency but the dependency's version is different, then npm will install the dependency in the package's local node_module folder.

Try the following. Both @hwbdev/nested-package and @hwbdev/nested-package-two have @hwbdev/say-something as dependencies with different semver specifier, but there does not exist a version that fulfills both specifier. If we run npm i @hwbdev/nested-package @hwbdev/nested-package-two, we will see that npm installs two versions of @hwbdev/say-something, one at the top-level, and one at the package's local node-module level.

If we now run npm i @hwbdev/nested-package @hwbdev/nested-package-two @hwbdev/[email protected], we will see @hwbdev/[email protected] is install at the top level, while there are two other versions installed locally, one in @hwbdev/nested-package and the other in @hwbdev/nested-package-two.

For more detail, see https://docs.npmjs.com/cli/v6/commands/npm-install#algorithm