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

anxiety

v1.1.0

Published

A cli to share our collective anxieties

Downloads

5

Readme

anxiety

a simple CLI to share our anxieties

usage

npx anxiety

## or

npm i -g anxiety
anxiety

y tho

anxiety is a part of my life and I've discovered it's a part of many other developers lives. Hopefully publishing a collaborative module of our collective anxieties can help normalize it for a fellow developer somewhere 💖

but you're polluting the namespace

ok, if you have a legitimately better use for the name please feel free to reach out to me and I'd be happy to hand it over to you as long as you publish starting at the next semver major after the modules current semver major. At the time of publishing there are nearly 1m published modules and anxiety has not yet been taken so this argument feels invalid ¯\_(ツ)_/¯

if you care about the namespace perhaps check out the JavaScript Standard Library proposal from TC39 that introduces a namespace to JavaScript. If adopted, Node.js could also follow suit and implement a namespace, as could registries. Support it if you care about this problem 💖