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

node-flex-serve

v0.0.2

Published

A lean, modern, and flexible node server

Downloads

923

Readme

node-flex-serve

A lean, modern, and flexible node server

Node Flex Serve's code is widely inspired from webpack-serve.

Getting Started

To begin, you'll need to install node-flex-serve:

$ npm install node-flex-serve

CLI

$ node-flex-serve --help

  Options
    --config            The node-flex-serve config to serve. Alias for <config>.
    --content           The path from which content will be served
                        Default: process.cwd()
    --help              Show usage information and the options listed here.
    --host              The host the app should bind to
    --http2             Instruct the server to use HTTP2
    --https-cert        Specify a cert to enable https. Must be paired with a key
    --https-key         Specify a key to enable https. Must be paired with a cert
    --https-pass        Specify a passphrase to enable https. Must be paired with a pfx file
    --https-pfx         Specify a pfx file to enable https. Must be paired with a passphrase
    --log-level         Limit all process console messages to a specific level and above
                        Levels: trace, debug, info, warn, error, silent
    --log-time          Instruct the logger for node-flex-serve and dependencies to display a timestamp
    --no-clipboard      Instructs the server not to copy the server URI to the clipboard when starting
    --open              Instruct the app to open in the default browser
    --open-app          The name of the app to open the app within, or an array
                        containing the app name and arguments for the app
    --open-path         The path with the app a browser should open to
    --port              The port the app should listen on
    --require, -r       Preload one or more modules before loading the add-ons configuration
    --version           Display the node-flex-serve version

  Examples
    $ node-flex-serve ./node-flex-serve.config.js
    $ node-flex-serve --config ./node-flex-serve.config.js --port 1337
    $ node-flex-serve --port 1337  # config can be omitted

Note: The CLI will use your local install of node-flex-serve when available, even when run globally.

Running the CLI

There are a few variations for using the base CLI command, and starting node-flex-serve:

  $ node-flex-serve ./webpnode-serveack.config.js
  $ node-flex-serve --config ./node-flex-serve.config.js

Those two commands are synonymous. Both instruct node-flex-serve to load the config from the specified path. We left the flag in there because some folks like to be verbose, so why not.

  $ node-flex-serve

node-flex-serve Config

You can store and define configuration / options for node-flex-serve in a number of different ways. This module leverages cosmiconfig, which allows you to define node-flex-serve options in the following ways:

  • in your package.json file in a serve property
  • in a .serverc or .serverc.json file, in either JSON or YML.
  • in a serve.config.js file which exports a CommonJS module.

Webpack Config serve Property

node-flex-serve supports the serve property in your config file, which may contain any of the supported options.

API

When using the API directly, the main entry point is the serve function, which is the default export of the module.

const serve = require('node-flex-serve');
const config = require('./node-flex-serve.config.js');

serve({ config });

serve([options])

Returns [a Promise which resolves] an Object containing:

  • close() (Function) - Closes the server and its dependencies.
  • on(eventName, fn) (Function) - Binds a serve event to a function. See Events.

options

Type: Object

Options for initializing and controlling the server provided.

addons

Please see Add-On Features.

context

Type: String|[String]
Default: process.cwd()

The path, or array of paths, from which static content will be served.

clipboard

Type: Boolean
Default: true

If true, the server will copy the server URI to the clipboard when the server is started.

host

Type: String
Default: 'localhost'

Sets the host that the server will listen on. eg. '10.10.10.1'

Note: This value must match any value specified for hot.host or hot.host.server, otherwise node-flex-serve will throw an error. This requirement ensures that the koa server and WebSocket server play nice together.

http2

Type: Boolean
Default: false

If using Node v9 or greater, setting this option to true will enable HTTP2 support.

https

Type: Object
Default: null

Passing this option will instruct node-flex-serve to create and serve the content through a secure server. The object should contain properties matching:

{
  key: fs.readFileSync('...key'),   // Private keys in PEM format.
  cert: fs.readFileSync('...cert'), // Cert chains in PEM format.
  pfx: <String>,                    // PFX or PKCS12 encoded private key and certificate chain.
  passphrase: <String>              // A shared passphrase used for a single private key and/or a PFX.
}

See the [Node documentation][https-opts] for more information. For SSL Certificate generation, please read the SSL Certificates for HTTPS section.

logLevel

Type: String
Default: info

Instructs node-flex-serve to output information to the console/terminal at levels higher than the specified level. Valid levels:

[
  'trace',
  'debug',
  'info',
  'warn',
  'error'
]
logTime

Type: Boolean
Default: false

Instruct node-flex-serve to prepend each line of log output with a [HH:mm:ss] timestamp.

on

Type: Object
Default: null

While running node-flex-serve from the command line, it can sometimes be useful to subscribe to events from the module's event bus within your config. This option can be used for that purpose. The option's value must be an Object matching a key:handler, String: Function pattern. eg:

on: {
  'listening': () => { console.log('listening'); }
}
open

Type: Boolean|Object
Default: false

Instruct the module to open the served bundle in a browser. Accepts an Object that matches:

{
  app: <String>, // The proper name of the browser app to open.
  path: <String> // The url path on the server to open.
}

Note: Using the open option will disable the clipboard option.

port

Type: Number
Default: 8080

The port the server should listen on.

Events

The server created by node-flex-serve emits select events which can be subscribed to. All events are emitted with a single Object parameter, containing named properties for relevant data.

For example:

const serve = require('node-flex-serve');
const config = require('./node-flex-serve.config.js');

serve({ config }).then((server) => {
  server.on('listening', ({ server, options }) => {
    console.log('happy fun time');
  });
});

listening

Arguments:
Koa server
Object options

Emitted when the server begins listening for connections.

SSL Certificates for HTTPS

We do recommend a path for users to generate their own SSL Certificates safely and efficiently. That path resides in devcert-cli; an excellent project that automates the creation of trusted SSL certificates that will work wonderfully with node-flex-serve.

Add-on Features

A core tenant of node-flex-serve is to stay lean in terms of feature set, and to empower users with familiar and easily portable patterns. This makes the module far easier to maintain, which ultimately benefits the user.

Luckily, flexibility baked into node-flex-serve makes it a snap to add-on features. You can leverage this by using the add option. The value of the option should be a Function matching the following signature:

add: (app, middleware, options) => {
  // ...
}

add Function Parameters

  • app The underlying Koa app
  • middleware An object containing accessor functions to call both the koa-static middleware.
  • options - The internal options object used by node-flex-serve

Some add-on patterns may require changing the order of middleware used in the app. For instance, if adding routes or using a separate router with the app where routes must be added last, you'll need to call the middleware functions early on. node-flex-serve recognizes these calls and will not execute them again. If these calls were omitted, node-flex-serve would execute both in the default, last in line, order.

add: (app, middleware, options) => {
  // since we're manipulating the order of middleware added, we need to handle
  // adding these two internal middleware functions.
  middleware.proxy();
  middleware.content();

  // router *must* be the last middleware added
  app.use(router.routes());
}

Listed below are some of the add-on patterns and recipes that can be found in docs/addons:

Contributing

We welcome your contributions! Please have a read of CONTRIBUTING.md for more information on how to get involved.

License

MIT