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

majid-azad

v1.0.1

Published

An example package to demonstrate Yarn

Readme

This is an example package that can be used to test Yarn.

It has the common default fields in its package.json, along with production and development dependencies as well that are specific to the package we have created.

The package.json

Default Package Fields

yarn init produces a default package.json similar to:

{
  "name": "example-yarn-package",
  "version": "1.0.0",
  "description": "An example package to demonstrate Yarn",
  "main": "index.js",
  "repository": {
    "url": "github.com/yarnpkg/example-yarn-package",
    "type": "git"
  },
  "author": "Yarn Contributors",
  "license": "BSD-2-Clause",
}

Custom Package Fields

You can add custom fields to your package.json as well. In our case, we have added 4 custom fields.

The scripts field are for any special scripts that you want to use when running yarn. For example, here we add a script called test that calls the Jest test runner because we added Jest tests to our Yarn package.

"scripts": {
  "test": "jest"
},

The dependencies field lists the other packages that this package is dependent upon. Our example package is dependent on Lodash since we use its multiply function.

"dependencies": {
  "lodash": "^4.16.2"
},

The devDependencies field lists the other packages that this package is dependent upon during development. Our example package is dependent on Jest since we created some Jest-enabled tests for our package.

"devDependencies": {
  "jest-cli": "15.1.1"
},

The jest field is a custom field specific to the Jest package we included as a dev dependency. In this case, we are testing in a node environment at the command-line.

"jest": {
  "testEnvironment": "node"
}

It is important to note that Lodash and Jest are not required for Yarn. They are just examples of what can be used when you are creating the code for your Yarn package.

Development

$ yarn install
$ yarn run test

Production

$ yarn install --production