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

suppress-warnings

v1.0.2

Published

Customizable suppression of node warnings.

Downloads

768

Readme

Suppress Warnings!

This module helps suppress some annoying warnings you may get that you're either too lazy to fix, or can't because it's not in a module you control.

The main function takes an array of "filter functions", as the first parameter, of which the arguments will be the same as process.emitWarning (It's also dynamic, so as node changes, it should also change.), the second parameter can be used to change the default behavior (blacklist), into a whitelist.

Examples:

JavaScript

// This must be called BEFORE any of the errors get sent, so require this first and run the function first before requiring any other modules
const SuppressWarnings = require("suppress-warnings");
// say you were getting a log like this: https://butts-are.cool/Code_-_Insiders_qeiR4Gtkyh.png
// (which is the warning that prompted me to make this)
// name: DeprecationWarning
// message: OutgoingMessage.prototype._headers is deprecated

// the first parameter is an array of filter functions
// return TRUE to hide the warning, and FALSE to pass it back to node

// the second parameter turns the default behavior (blacklist) into a whitelist
// where TRUE to pass it to node, and FALSE to hide it
SuppressWarnings([
	// warning can be an Error object or a string
	// name is always a string (can be absent)
	// I really don't know what ctor is, but it's in the ts definition
	(warning, name, ctor) => name === "DeprecationWarning" && warning.toString() === "OutgoingMessage.prototype._headers is deprecated"
]);

TypeScript

// This must be called BEFORE any of the errors get sent, so require this first and run the function first before requiring any other modules
import SuppressWarnings from "suppress-warnings";

// this is all the same, see JavaScript version for details

SuppressWarnings([
	(warning, name, ctor) => name === "DeprecationWarning" && warning.toString() === "OutgoingMessage.prototype._headers is deprecated"
]);