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

@gitlab/noop

v1.0.0

Published

This is a noop dependency to be able to prune parts of a dependency graph.

Downloads

47,939

Readme

@gitlab/noop

The idea behind this package is to be able to prune subtrees of dependencies which you might not need.

Reasons for why you might want to do this:

  1. Some dependencies (e.g. treesitter) ship a node/server and a browser component. You might not be interested in the server component, so you could prune the node/server subtree of dependencies.
  2. A particular part of dependencies might not be problematic and leading to oddities. One particular example is the glob package which ships a CLI interface which has some ESM-dependencies. One can reduce the dependency graph by quite a bit

Usage

The different package managers have different resolution features.

npm@v10

overrides is the native npm feature to override the version of a package. You can target sub-dependencies:

Example:

{
  "overrides": {
    "glob": {
      "jackspeak": "npm:@gitlab/[email protected]"
    }
  }
}

yarn@v1

Use Selective dependency resolutions and add a resolutions field to the package.json. The resoltions field allows pretty accurate sub-selection of dependencies.

Example:

{
  "resolutions": {
    "glob/jackspeak": "npm:@gitlab/[email protected]"
  }
}

yarn@v4

You can set the resolution manually with e.g.

yarn set resolution 'jackspeak@npm:^2.3.5' 'npm:@gitlab/[email protected]'

which will only update yarn.lock. Alternatively, you can update the package.json as well, which is a little more verbose:

Example:

{
  "resolutions": {
    "jackspeak@npm:^2.3.5": "npm:@gitlab/[email protected]"
  }
}

pnpm@v9

pnpm.overrides is the canonical way to define a resolution for pnpm:

NOTE: With [email protected], you don't need this package. You can simply use - as an override!

For older versions you can use this example:

{
  "pnpm": {
    "overrides": {
      "glob>jackspeak": "npm:@gitlab/[email protected]"
    }
  }
}

bun@v1

Bun supports both npm style overrides and yarn@1 style resolutions.

Example:

{
  "resolutions": {
    "jackspeak": "npm:@gitlab/[email protected]"
  }
}