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

appup

v1.3.0

Published

CLI to launch apps that use an express main server and an optional restif api server.

Downloads

25

Readme

appup build status

CLI to launch apps that use an express main server and an optional restif api server.

Servers are super stable with the help of domains and the cluster module. This means in practice that when a request causes an unhandled error a 500 response is sent, the server shut down gracefully and a new one spun up.

Two servers are spun up originally for each port, so that while one is restarted, the other one keeps servicing incoming requests.

Installation

npm install appup

CLI

appup [options] file

Options:
  --pages      port to start pages server on
  --watchdir   directory to watch for client side JavaScript changes in order to automatically refresh
  --dedupe     if set it will [dynamically dedupe] (https://github.com/thlorenz/dynamic-dedupe)
	             all modules as they are being required to work around the fact that symlinks break `npm dedupe`
  --api        port to start api server on
  --apihost    address at which api server is hosted [default: "localhost"]
  --tunnel     sets up local tunnel pointing to pages port and logs url to connect to from remote client
  --config     point to a config file to override routes, etc. for the pages and api server
  --nocluster  if set, single servers are launched instead of a cluster of them, which maybe preferred during development

API

generated with docme

config

The config needs to provide either or all of the following properties on the module exports object:

  • bundleOpts: {Object} options passed to browserify().bundle(options)
  • initBrowserify: {Function} invoked with browserify that needs to return a browserify instance that can be initialized according to our needs
  • initPages {Function} invoked with (pagesApp, express, apiServerInfo) where apiServerInfo is { host: {string}, port: {number} }
  • postInitPages {Function} invoked with (pagesApp, pagesServer, express) where pagesServer is the result of pagesApp.listen()
  • pagesSend500 {Function} invoked with (req, res, err) to allow responding with a 500 error before worker gets taken offline and another one is launched
  • initApi {Function} invoked with (apiApp, restify)
  • postInitApi {Function} invoked with (apiApp, apiServer, restify) where apiServer is the result of apiApp.listen()
  • apiSend500 {Function} invoked with (req, res, err) to allow responding with a 500 error before worker gets taken offline and another one is launched
  • events {EventEmitter} used to emit info and error events, if not provided messages are logged to the console instead

Example config

// Bundle options
exports.bundleOpts = { debug: true, insertGlobals: false };

exports.initBrowserify = function (browserify) {
  return browserify().transform('hbsfy');
};

// Server options

// Pages
exports.initPages = function (pagesApp, express, apiServerInfo) {
  pagesApp.use(core.renderViewMiddleware(viewPath, { title: 'core' }));
};

exports.postInitPages = function (pagesApp, pagesServer, express) {
};

// API 
exports.initApi = function (apiApp, restify) {
};

exports.postInitApi = function (apiApp, apiServer, restify) {
};

License

MIT