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 🙏

© 2026 – Pkg Stats / Ryan Hefner

forewarn

v1.0.2

Published

Scoped and styled warning logger

Downloads

9

Readme

forewarn

Scoped and styled warning logger. Best used sparingly, forewarn writes a message to console unless a condition is falsy or NODE_ENV is production. It's meant to advise consumers of your module when some argument is invalid, but you have an alternative code path to follow. Meaning: instead of throwing an error and breaking the flow, you adapt, and through forewarn, you help developers prevent the situation in the future.

npm status Dependency status

example

about

This module is adapted from React's warning function:

Similar to invariant but only logs a warning if the condition is not met. This can be used to log issues in development environments in critical paths. Removing the logging code for production environments will keep the same logic and follow the same code paths.

Differences from React's warning:

  • Scoped like debug
  • The warning message is styled if the execution environment is Chrome, Electron, Firefox with Firebug or Node.js
  • The condition argument has flipped polarity and is made explicit (because it's easier to read IMHO):
    • warn.when(3 !== 3, 'Three should be three') reads as "warn if 3 does not equal 3"
    • warn('Three should be three') always warns.
  • Arguments are passed to console.warn as is, so you can use all modifiers (depending on environment) instead of just %s and an arbitrary number of extra arguments.

example

const warn = require('forewarn')('my-module')

let path = ['a', 'b']
  , length = path.length
  , minimum = 3

warn.when( length < minimum
         ,'Ignoring invalid path %o because length %d is less than %d'
         , path, length, minimum )

api

warn = forewarn(scope)

Create a warn function. Messages will be prefixed with the string scope (usually the name of your module). Returns a noop in production.

warn(format, ...args)

Log a warning.

warn.when(condition, format, ...args)

Log a warning if condition is truthy.

install

With npm do:

npm install forewarn

license

MIT © Vincent Weevers