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

@joycostudio/generic

v0.1.1

Published

The generic template library starter from joyco.studio

Downloads

3

Readme

WTF is this?

A generic library template starter for new JOYCO libs.

❗️ MUST DO ON TEMPLATE FORK ❗️

This is a sample package that serves as a template. If you are forking from it you NEED to update the package.json "name" field. Also DELETE the .changeset/ folder and the CHANGELOG.md file to start your library versioning history from the very start.

👀 Good to know

If you DON't need react as a peer dependency you NEED to delete it.

# 1. Remove both the devDependencies and peerDependencies
pnpm remove @types/react react

Then manually remove the peerDependencies section from package.json and also check eslint.config.js, tsconfig.json.

🦋 Version Management

This library uses Changesets to manage versions and publish releases. Here's how to use it:

Adding a changeset

When you make changes that need to be released:

pnpm changeset

This will prompt you to:

  1. Select which packages you want to include in the changeset
  2. Choose whether it's a major/minor/patch bump
  3. Provide a summary of the changes

Creating a release

To create a new version and update the changelog:

# 1. Create new versions of packages
pnpm changeset version

# 2. Build the packages
pnpm build

# 3. Publish to npm
pnpm changeset publish

Remember to commit all changes after creating a release.