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

hot-module-replacement

v3.0.4

Published

Hot module replacement for node.js

Downloads

405

Readme

hot-module-replacement

Hot module replacement for node.js

This module tries to mimic webpack HMR API

Installation

  npm install --save-dev hot-module-replacement

Usage

Put this code somewhere in your code to initialise hot reload

require('hot-module-replacement')({
  // options are optional
  ignore: /node_modules/  // regexp to decide if module should be ignored; also can be a function accepting string and returning true/false
})

You need to explicitly mark any subtree as 'hot reloadable' by calling hot.accept()

  let foo = require('./util/foo.js');

  if (module.hot) { 
    module.hot.accept('./util/foo', () => {
      // if foo.js or any files that foo.js depend on are modified this callback is invoked
      foo = require('./util/foo.js'); // by this time module cache entry for 'foo' already cleaned and module reloaded, requiring again is the easiest way of geting reference to new module. We need to assign it to local foo variable to make our local code in this file aware of it.
    })
  }

Similar projects:

  • https://github.com/yyrdl/dload ( forces you to use own module api for replaceables modules )
  • https://github.com/rlindskog/solit ( transpiles all files on start )
  • https://github.com/fgnass/node-dev

webpack hmr on the server

  • https://github.com/palmerhq/backpack
  • https://hackernoon.com/hot-reload-all-the-things-ec0fed8ab0
  • https://github.com/jaredpalmer/razzle
  • https://github.com/jlongster/backend-with-webpack ( and http://jlongster.com/Backend-Apps-with-Webpack--Part-III )