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

dont-really

v1.0.2

Published

easily publish throwaway versions of a package to a local npm registry

Downloads

10

Readme

dont-really

Easily publish throwaway versions of a package to a local npm registry.

The problem

You are making changes to a library that is used by other packages. You want a quick way to see how the changes impact your consumers.

Adding the library using the file:// prefix copies whole directory into the package's node modules. This is different to adding the library from a remote registry. In the remote case, only files that have been published are put into the package's node modules. These published files are controlled by the library's package.json and .npmignore files.

These difference can lead to errors that are false positives, or worse, errors that are undiscovered. 😡

The solution

dont-really is a utility that provides an easy way of publishing to and adding packages from a local npm registry. This makes it painless to publish local versions of a library and add those versions in other packages. Your library will be added in the same way it would be in the wild. You are now consuming your library in the same way your users do. Hurray! 🙌

Usage

Substitute yarn or npm with dont-really.

From the directory of the package you want to publish locally:

dont-really publish

To add the package from the local registry:

dont-really add [options] <package-name>

Or if you are using npm:

dont-really install [options] <package-name>

Installation

This package uses the awesome Docker image provided by verdaccio to create the local registry.

Step one is to ensure you have Docker installed and running. If you need to install Docker, follow the Docker installation docs to get setup. Verify Docker is running with:

docker --version

Download and start the verdaccio Docker image by running:

docker run -it -d --name verdaccio -p 4873:4873 verdaccio/verdaccio

You can now visit the local registry at http://localhost:4873.

Add yourself as a user on the local registry with:

npm adduser --registry http://localhost:4873

This allows you to publish packages to the local registry.

Finally run:

yarn global add dont-really

Thats it! 🎉