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

@tigre/dev-warning

v1.0.0

Published

Provides development only warning messages. Messages are designed to only trigger a single time per application refresh to avoid being annoying.

Downloads

3

Readme

@tigre/dev-warning

A simple, tiny library for enabling development only warnings to be easily published to the console.

The library automatically stops producing the warnings when built in production mode. To build in production mode use whichever bundler you like and ensure that process.env.NODE_ENV is set to equal production.

This module does nothing useful in production mode, so if you have tree-shaking enabled you can wrap any call to this module with:

import createDevWarning from "@tigre/dev-warning";

if (process.env.NODE_ENV === "development") {

	// Perform the check that needs a development warning
	if (/* someone made a development mistake */) {
		createDevWarning(
			"<The error message>", 		// A useful and descriptive error message
			{ 							// This object is optional, when included it will only 
										// display the message once per unique set of switches in the file
										// All fields in this object are optional.
				file: __filename, 		// Typically useful to include, `__filename` needs to be enabled in webpack
				warning: "warning", 	// Also very useful unless a single warning possible
				detail: "detail",
				extra: "extra"
			}, 
			{ 
				more: "details" 		// Optional object that gets printed in the console.warn call.
										//  This can be used to provide extra diagnostic details to solve the problem.
			}
		);
	}
}

Recommended usage:

import createDevWarning from "@tigre/dev-warning";

// Easy, repeats every time
if (process.env.NODE_ENV === "development") {
	createDevWarning("Repeating warning");
}

// Medium, only triggers once
if (process.env.NODE_ENV === "development") {
	createDevWarning("warning", {
		file: __filename,
		warning: "single time"
	});
}

// Detailed, only triggers once, gives lots of how to fix details
if (process.env.NODE_ENV === "development") {
	createDevWarning("warning", {
		file: __filename,
		warning: "single time"
	}, {
		causedBy: "information",
		reason: "bad"
	});
}