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

@gustavnikolaj/node-invariant

v1.0.0

Published

All other invariant-style modules I have found are optimized for the browser and will typically use `process.env.NODE_ENV === 'production'` as a hook to get their minifiers to remove the expensive debug code. This makes sense for frontend code where you d

Downloads

3

Readme

Invariant module for node.js

All other invariant-style modules I have found are optimized for the browser and will typically use process.env.NODE_ENV === 'production' as a hook to get their minifiers to remove the expensive debug code. This makes sense for frontend code where you don't need the explanations in the messages, but it is really annoying for server code where you don't need to optimize that much for size - it just makes debugging harder.

The only one I found which didn't have this problem gave polluted stack traces, so I just quickly wrangled this together.

Installation

$ npm install @gustavnikolaj/node-invariant

Usage

const invariant = require('@gustavnikolaj/node-invariant')

invariant(myCondition, 'My invariant message');

// if myCondition is falsy:
//
// InvariantViolation: My invariant message
//     at ~/Projects/my-app/test.js

Why not just assert?

The core assert module almost works just as well, but it generates too noisy errors and have a lot of extra complexity going on.

The reason you would use a module like this is not for errors facing the caller of your web application or REST API, it's for other developers, or poor OPS-people trying to get your application to run.

If you have required secrets that must be passed in as environemnt variables, you could use this module:

// filename: config.js

const invariant = require('@gustavnikolaj/node-invariant');

invariant(
    typeof process.env.DB_PASS === 'string' && process.env.DB_PASS.length,
    'Missing environment variable DB_PASS'
);

module.exports = {
  database: {
    // ...
    password: process.env.DATABASE_PASSWORD
  }
};

If the person trying to start your application forgot passing in the DB_PASS variable, they will now get a nice error:

InvariantViolation: Missing environment variable DB_PASS
    at Object.<anonymous> (~/Projects/my-app/start-server.js:1:14)

The same error but with assert would look like this:

AssertionError [ERR_ASSERTION]: Missing environment variable DB_PASS
    at Object.<anonymous> (/Users/John/Projects/my-app/start-server.js:1:14)
    at Module._compile (internal/modules/cjs/loader.js:1137:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
    at Module.load (internal/modules/cjs/loader.js:985:32)
    at Function.Module._load (internal/modules/cjs/loader.js:878:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47 {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}