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

warm

v1.0.2

Published

warm up node modules before using

Downloads

6

Readme

warm

Build Status via Travis CI NPM version Coverage Status

This node.js module is useful if you want to load other modules and be sure all warming code is executed before you continue.

Quick usage

Install module into own project

# npm install --save warm

Create new class and call .parallel method

Warm = requre('warm');

new Warm('./database', './redis').parallel(function (err) {
  if(err) { throw err; }
  console.log('Initial code was executed in all described modules');
});

Modules database and redis should return special method (.init by default), which resolve promise or call callback on finish. See Modules

Options

You can pass additional options like plain object: new Warm({ ... }, 'module1', ...):

| Name | Default | Description | | ------------- |:----------:| -----| | .expect | promise | will init method inform about finish with promise (reject/resolve it), or will fire callback with error (expect: 'callback') | .path | '' | prefix for requiring modules | .strict | true | should return error if init method not found in module | .init | init | init method name

Samples

Warm = requre('warm');

// load modules in array or additional parameters with options
options1 = {
  expect: 'callback'
}
options2 = {
  strict: true
}
new Warm(options1, ['./module1', './module2'], './module3', options2).parallel(console.log);

// execute already loaded module
new Warm(require('./module3')).parallel(console.log);

// handle promise
new Warm('./module1').parallel().then(function () {
  console.log('loaded');
}).catch(function (err) {
  console.log('error:', err);
})

Modules

Module should contain method .init (or other, described in options) which will return promise or file callback. Example:

module.exports = function () {
  return 'i will not fire';
};
module.exports.init = function (callback) {
  setTimeout(function () {
    console.log('>>> i will fire durning warming');
    callback();
  }, 100);
};

Additional samples can be found in test folder