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

initializer

v0.0.3

Published

Helps to initialize your project.

Downloads

28

Readme

Initializer

Helps to initialize your project, optionally specifiying priority and/or a folder to load scripts from. I was inspired by the idea from Jared Hanson's Bootable project.

Getting Started


Initializer was built to help you out, not get in your way. There are very minor differences you'll need to make in your code and chances are you've already accomidated some of them such as exporting a function.

Install with npm: npm install initializer --save

Create a folder to house all your startup scripts aka initializers

+run.js
|
+initializers/
    |
    +-server.js
    +-database.js
    +-otherasyncstuff.js

Each file should at the very least export a function (but it's completely up to you)

Here's a sample of what database.js might look like:

// import any modules
var db = require('db');

module.exports = function database (done) {

    // establish a connection to your database
    db.connect('localhost', done);

};

// optionally set a priority for this initializer,
// the lower the number, the sooner it executes
module.exports.priority = 10;

And here's what your run.js might look like:

var initializer = require('initializer');

// pass the folder as the first argument to search for initializers and start initializing
var init = initializer('./initializers').start();

Other Examples


You can also add a function right from the function instance.

var initializer = require('initializer');

var init = initializer();

init.add(function first (next) {
    console.log('starting misc init');
    setTimeout(function () {
        next();
    }, 1000);
});

init.start();

Chaining works too

var init = require('initializer');

init().add(function(){console.log('hello')}).start();

Initializer is also an instance of EventEmitter

var init = initializer('./initializers');

init.on('error', function (err) {
    console.error(err);
});

init.start();

TODO


  • create tests with mocha
  • detailed documentation
  • added before/after events when running each initializer

License

MIT