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

startup

v1.1.1

Published

Node.js HTTP app runner

Downloads

1,316

Readme

startup

Node.js HTTP app runner

Features

Usage

All startup requires is an exported http app:

Express Example

var express = require("express");

// Export the express app
var app = module.exports = express();

app.get("/", function (req, res){
  res.send("Hello!");
});

Connect Example

var connect = require("connect");

// Export the connect app
var app = module.exports = connect();

app.use(function (req, res, next){
  res.send("Hello!");
});

Vanilla HTTP Example

var http = require("http");

// Create the http server
var server = http.createServer(function (req, res){
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.end("Hello!");
});

// Export it
module.exports = server;

To start the app, just run:

startup start

and startup will bind to the PORT environment variable.

Sockjs Example

To install any handlers needed, sockjs for example, listen for the ready event:

var express = require("express")
  , sockjs = require("sockjs");

// Export the express app
var app = module.exports = express();

// Setup the sockjs server
var echo = sockjs.createServer();
echo.on('connection', function(conn) {
  conn.on('data', function(message) {
    conn.write(message);
  });
  conn.on('close', function() {});
});

app.get("/", function (req, res){
  res.send("Hello!");
});

// Install the handlers
app.on("ready", function(server){
  echo.installHandlers(server, {prefix: "/echo"});
});

Listening Callback

To know when the server is listening on a port, bind to the listening event:

var express = require("express");

// Export the express app
var app = module.exports = express();

app.get("/", function (req, res){
  res.send("Hello!");
});

app.on("listening", function(server){
  console.log("My app is listening");
});

Commands

###startup start

Starts app listening on the PORT environment variable.

###startup middleware

Lists loaded middleware (express and connect only) without running the app.

###startup routes

Lists loaded middleware (express only) without running the app.

###startup settings

Lists app settings (express only) without running the app.

Port Binding

startup will look for the PORT environment variable and try to bind to it. If not value is found, it defaults to 3000. You can also set it by executing startup start -P <port>.

Hot-Reload

To enable hot-reload, set the NODE_ENV environment variable to development. You may also specify --dev to force it.

Read more about node-dev, the tool startup uses.

Domains

Domains were introducted in v0.8 and act as a way to isolate uncaught exceptions in a process. This proves useful for http servers when we want each request to be handled in a unique domain, as to not crash the whole server.

Setting it up requires a bit of boilerplate code that comes built in to startup.

You can also provide a custom error handler for when you do get an uncaught exception by exporting errorHandler in your app:

var express = require("express");

// Export the express app
var app = module.exports = express();

app.get("/", function (req, res){
  res.send("Hello!")
});

module.exports.errorHandler = function (err, req, res) {
  res.send("There was an error!");
};

Cluster

Cluster allows a server to take advantage of all of the cores on a system instead of being limited by node's single thread. Cluster mode is enabled by default in production.

SIGTERM and SIGINT

startup reacts to system messages to enable clean exits. When it receives a SIGTERM it stops accepting connections and gives all of the current connections 3 seconds (overridable by setting SOCKET_TIMEOUT) to clean up and shut down. In environments like heroku it is very important the server reacts to these messages since the platform can shut it down at any time.