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 🙏

© 2026 – Pkg Stats / Ryan Hefner

express-app-boot

v0.0.4

Published

Boot utility for Express App

Readme

express-app-boot

A simple Express App utility to bootstrap the server.

Install

sudo npm install --save express-app-boot

Usage


var app = require('express')();
var ROOT_DIR = __dirname;
//boot configuration will be loaded at ROOT_DIR
var boot = require('express-app-boot')(ROOT_DIR);

var PORT = process.env.PORT || 3000;
//second parameter stands for dir path of boot scripts
boot(app, 'boot');
/*...*/
//maybe some custom logic before start
app.beforeStart(function(app){
  /*...*/
});
//At the end, start the server
if(require.main === module){
    app.start(function(app){
      //start logic
      app.listen(PORT);
    });
} else {
//In case you want to use app in your tests.
  module.exports = app;
}
 

Configuration

root_dir

  • dir path of configuration files, passed in when init boot function

configuration files

config.yml

  • Put global application options in this file, will be loaded and attacthed to app with the key 'appConfig'.

boot.yml

  • Boot configuration file, contains boot task items. These items are grouped into before and after phases respectively.

Task in before phase executes before custom execution logic(app.beforeStart), and after phase task executes when app.start is invoked.

for example,

---
before:
  - path: init
    name: initializing app
    params: 
      msg: start default booting
  - path: session
    name: configuring session 
    params:
      key: default-session
      collection: session
  - path: auth
    name: configuring authentication
  - path: parse
    name: configuring body parse
  - path: view
    name: setting view engine
    params:
      path: views
      ext: html

after:
  - path: @express-routes-loader
    name: initializing application routes
    params: ../routes
  - path: error
    name: setting error handlers

boot item should include path property, which identifies the boot script location. Path starts with @ stands for a npm module name, otherwise is relative to the boot_dir.

Task within a phase will executes in the order in which it is registered.

Changelog

Latest:

0.0.1

  • Initial Commit