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

require-again

v2.0.0

Published

A simple module that makes ignoring the node require cache easy.

Downloads

8,417

Readme

require-again

A simple module that makes ignoring the node require cache easy.

Why?

Say you have a file that has slightly different behavior when running in a production environment. Like so:

var isProd = process.env.NODE_ENV === 'production'

if (isProd) {
  // do special prod stuff
} else {
  // do non-prod stuff
}

module.exports = myModule

When you require this module in your test files, it'll run the isProd check once and then cache that version of the module. This makes it difficult to test both behaviors. require-again allows you to get a freshly required version of the module.

Requiring the module normally after using requireAgain will return the original cached version of the module.

Usage

Example using Mocha

var requireAgain = require('require-again')
var pathToModule = './path/to/module'

describe('some test', function () {
  context('prod behavior', function () {
    before(function () {
      this.oldEnv = process.env.NODE_ENV
      process.env.NODE_ENV = 'production'

      this.module = requireAgain(pathToModule)
    })

    after(function () {
      process.env.NODE_ENV = this.oldEnv
    })

    it('does something in a production environment', function () {
      // tests
    })
  })

  context('non-prod behavior', function () {
    before(function () {
      this.oldEnv = process.env.NODE_ENV
      process.env.NODE_ENV = 'dev'

      this.module = requireAgain(pathToModule)
    })

    after(function () {
      process.env.NODE_ENV = this.oldEnv
    })

    it('does something in a development environment', function () {
      // tests
    })
  })
})

Testing

This module is tested in Node versions:

  • 4.x.x
  • 5.x.x
  • 6.x.x

Changelog

See releases for a detailed changelog.