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

hold-place

v0.1.2

Published

A CLI tool to publish an auto-generated barebones package to the npm registry under the given name.

Downloads

3

Readme

A simple CLI tool to quickly publish a barebones package to the npm registry under a given name.

Installation

It is recommended to install this package globally, as its usage is independant and unrelated to other locally installed packages.

npm i -g hold-place

You can also temporarily install the package to a central cache with npx instead of installing it globally. To do so, skip the above installation step, and simply prefix all usage commands with npx.

Usage

This tool will publish a package to npm as the npm account of the credentials stored in execution environment (i.e. the npm account logged-in on your client).

To publish a package, you must have a user on the npm registry. If you don't have one, you can create it 2 ways:

  • On the npm website
  • Using npm adduser

Note: If you created one on the site, use npm login to store the credentials on the client.

Once you have created a user and logged in, you can use npm config ls to ensure that the credentials are stored on your client. You can also check that your user has been added to the registry by going to https://npmjs.com/~username.

Source: http://npm.github.io/installation-setup-docs/installing/logging-in-and-out.html


To generate and publish the package, specify the name under which to publish on the npm registry as the first CLI argument.

hold-place some-coveted-namespace

or, if using npx

npx hold-place some-coveted-namespace

(and accept the prompts to install the package if it is not already found in the central cache.)

TODO

Future updates will improve configurability, by supporting CLI options to configure the auto-generated package source code, namely adding an informative default README.md file and allowing the package initialization to be interactive.

Support will also be added for a dry-run to check whether a namespace is available (whether publishing will succeed).