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

warntf

v0.1.0

Published

<center> <h1>⚠️ <a href="https://warning.wtf">warning.wtf</a> ⚠️ </h1> </center>

Downloads

1

Readme

Everyday, we developers see dozens of warnings and choose to ignore them (or do we have a choice?).

This started as a random ~~tweet~~ X but then i thought, if we don't don't do anything, would it be an ethernal fight between library authors that care to add those warning lines and developers that either ignore them or have no choice but to ignore them. And we love to know why. And who is to point fingure to?

👉 Have you come from a console warning here?

We love to hear your opinion. Please share them in this discussion.

And sorry for sorry for disturbing you. You can disable this if you want just set NO_WTF_WARN environment variable or put this in your code

globalThis.NO_WTF_WARN = true;

🧙 How to ~~shame~~use?

// Dynamic import
// Works in both CJS and ESM
import("warntf/setup");

// ESM
import "warntf/setup";

// CJS
require("warntf/setup");

❓ How it works

When warntf/setup is imported, we hook to console.warn calls from any library and after each 5 warnings by default, we show this warning.

⚙️ Configuration

There is not much but there are two:

  • NO_WTF_WARN environment variable or global constant to disable this
  • WTF_WARN_FREQ environment variable or global constant to set frequency (default is 5)

🙌 Join the effort!

Do you have ideas to improve this project or how else we can approach?

Use issues or discussions to join the crew!

we are hiring meme

Development

  • Clone this repository
  • Install latest LTS version of Node.js
  • Enable Corepack using corepack enable
  • Install dependencies using pnpm install
  • Test with pnpm play

License

Made with 💛 Published under MIT License.