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

@patternslib/dev

v4.3.0

Published

Development base files for working with Patternslib and add-ons.

Readme

Development helpers and config for Patternslib and add-ons.

This repository includes base files which are extended in Patternslib, Mockup or other projects.

It includes a Makefile which helps in installing and releasing packages.

Upgrading

Run make upgrade in your project.

Alternatively, if there is a new @patternslib/dev version installed, the postinstall package.json script will automatically run make upgrade in the directory where package installer was invoked, that is your project directory which depends on @patternslib/dev.

Migrating a consuming package to pnpm

Installing @patternslib/dev does not require switching your project from Yarn to pnpm. If you choose to migrate, update the consuming project's configuration and workflows explicitly. The shared Makefile uses pnpm for installation and for running build, test, and start scripts.

  1. Pin the pnpm version you intend to use and pin it in your project's package.json:

    "packageManager": "[email protected]",
  2. Add a pnpm-workspace.yaml file at the project's workspace root:

    # No nested node_modules for Module Federation.
    shamefullyHoist: true

    You might also want to include the following to allow to build "@patternslib/dev" and to include releases of "@patternslib/dev" which are younger than the "minimumReleaseAge":

    allowBuilds:
        "@patternslib/dev": true
    
    minimumReleaseAgeExclude:
        - "@patternslib/dev"

    For more information, see the pnpm configuration reference.

  3. Change the yarn references in the Makefile to use pnpm.

PNPM ?= npx pnpm

-include node_modules/@patternslib/dev/Makefile

.PHONY: install
pnpm-lock.yaml install:
	$(PNPM) install

If you use yarn link or yarn unlink in your Makefile, update it to fit the new pnpm syntax.

  1. You might need to include pnpm to the transformIgnorePatterns field in Jest configuration to make the tests pass. This files jest.setup.js for an example.

  2. Update the CI configuration to use the pnpm cache - see this projects .github/workflows/test.yml.

  3. Run make install, add pnpm-lock.yaml to the git repository and remove yarn.lock.

Code style

The release process based on release-it includes automatic changelog generation via conventional-commit, commitlint and a git pre-commit hook. Please check the code style guide for the commit specification!