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

@hanseltime/dev-npm-registry-tools

v1.0.0

Published

Simple collection of scripts to allow for local cross repository development

Downloads

2

Readme

dev-npm-registry-tools

This package presents tools for developing packages between repositories locally. This is particularly important when you are trying to change a package whose most affected use case is in another repo. Rather than going through full release cycles, you can set up a local developer registry and then publish and load from it.

Important - This package currently only supports yarn v2. Please contribue yarn v1/npm equivalents when necessary.

Setting up a local registry

These scripts rely on the repository that you're supposed to clone and run a registry from. Registry Project

You will also need to create a user and password (if you don't want to use the default "admin":"admin")

Creating a user

Publishing your package locally

If you are in a package that you would like to package to the local repo for pulling into your supporting project, you will need to run:

yarn local-publish

Please check the help for other options.