Nodecaf

Docs for version v0.13.x

Nodecaf is a light framework for developing RESTful Apps in a quick and convenient manner.

Highlights

• URL path pattern routing
• Each route accepts a single function as an argument (see why)
• Useful handler arguments
• Optional automatic body parsing for popular formats
• Support for Settings files or objects with straightforward layering
• Stdout logging
• Seamless support for async functions as route handlers
• Uncaught exceptions in routes always produce proper REST responses
• Assertions for readable RESTful error handling
• Facility for exposing global objects to all routes (eg.: database connections)
• CORS Settings
• Allow calling all endpoints programmatically with complete feature parity (awesome for unit testing)
• Helper to handle WebSocket connections.
• Helpful command line interface

Get Started

1. Install the cli utilities: npm i -P -g nodecaf-cli.
2. Create a skelleton project with: nodecaf init my-project.
3. Add your globals in lib/main.js

1const Nodecaf = require('nodecaf');
2const routes = require('./routes');
3
4module.exports = () => new Nodecaf({
5
6    // Optionally bind to a given port
7    conf: { port: 80 },
8
9    // Load your routes.
10    routes,
11
12    // Perform your server initialization logic.
13    async startup({ conf, log, call }){
14
15    },
16
17    // Perform your server finalization logic.
18    async shutdown({ conf, log, call }){
19
20    }
21});

4. Add your routes in lib/routes.js

1const { post, get, del, head, patch, put, all } = require('nodecaf');
2
3module.exports = [
4
5    // Define routes with their handler functions (async or regular no matter).
6    get('/foo/:f/bar/:b', FooBar.read),
7    post('/foo/:f/bar', FooBar.write),
8    // ...
9
10    // This route runs whenever there is no other path match
11    all(Foo.atLast)
12];

5. In your app root directory run with: nodecaf run .

How to Run my App

There are a few supported ways of running your app dependng on the type of environment you are targeting.

Running on development machine

1. You should use the CLI (npm i -P -g nodecaf-cli)
2. Run: nodecaf run path/to/your/app
3. Optionally pass config files with -c path/to/config
4. Optionally enable live reload with -r

Running on Docker for development

• Build the auto-generated Dockerfile
• Bind the port you are going to listen to
• Create a bind mount to your config files
• Reference your config files in the command
• Create a bind mount to your app directory targeting /app inside the container
• Run the container

Or use this example compose configuration:

1my-app:
2  build: ./my-app
3  command: -c /my-conf.toml
4  ports:
5    - 80:8080
6  volumes:
7    - ./my-conf.toml:/my-conf.toml
8    - ./my-app:/app
9  environment:
10    NODE_ENV: ''

Running on Docker for production

• Build and run the auto-generated Dockerfile in the same fashion as development
• You should NOT setup a volume in production so you just use the source code baked in the image
• Ensure all configuration files referenced in the command are accessible inside the container
• Run the container

Running as a node module

Your Nodecaf app is exported as a regular node module, so it can run as a dependency in another project

1let myApp = require('my-app');
2
3(async function(){
4
5    let app = myApp();
6    await app.start();
7
8    let res = await app.trigger('/');
9
10    await app.stop();
11})();

Reporting Bugs or Vulnerabilities

If you have found any problems with Nodecaf, please:

1. Open an issue.
2. Describe what happened and how.
3. Also in the issue text, reference the label ~bug or ~security.

We will make sure to take a look when time allows us.

Proposing Features

If you wish to get that awesome feature or have some advice for us, please:

1. Open an issue.
2. Describe your ideas.
3. Also in the issue text, reference the label ~proposal.

Contributing

If you have spotted any enhancements to be made and is willing to get your hands dirty about it, fork us and submit your merge request so we can collaborate effectively.

• For coding style, we provide an ESLint configuration file in the root of the repository.
• All commits are submit to SAST and Dependency Scanning as well as Code Quality analisys, so expect to be boarded on your MRs.

Manual

Formerly based on Express, Nodecaf has a simpler approach to defining routes, offloading much of the complexity to the already existing code partitioning idioms (i.e. functions). Check out how to use all the awesome goodies Nodecaf introduces.

Handler Args

In this manual we address as handler args the keys in the object passed as the only argument of any route handler function. The code below shows all handler args exposed by Nodecaf:

1function({ method, path, res, query, params, body, conf, log, headers, call, websocket }){
2    // Do your stuff.
3}

Quick reference:

• res: An object containing the functions to send a response to the client.
• path, method, query, params, body, headers: Properties of the request. They contain respectively the requested path, HTTP method, query string, the URL parameters, and the request body data.
• conf: This object contains the entire application configuration data.
• log: A logger instance. Use it to log events of your application.
• call: Calls any user function passing the handler args as the first argument. Signature: call(userFunc, ...extraArgs).
• Also all keys of the globally exposed object are available as handler args for all routes.

Settings File

Nodecaf allow you to read a configuration file and use it's data in all routes and server configuration.

Use this feature to manage:

• external services data such as database credentials
• Nodecaf settings such as cors and logging
• Your own server application settings for your users

Suported config formats: TOML, YAML, JSON, CSON

Check out how to generate a project with configuration file already plugged in

To load a config file in your app, use the -c flag through the CLI pointing to your conf file path: nodecaf run -c my/conf/path.toml my/app

You can use the config data through it's handler arg in all route handlers as follows:

1post('/foo', function({ conf }){
2    console.log(conf.key); //=> 'value'
3})

Config data can also be passed as an object to the app constructor in lib/main.js:

1module.exports = () => new Nodecaf({ conf: { key: 'value' } });

Or a file path if you want to have a fixed config file for setting defaults or any other reason:

1module.exports = () => new Nodecaf({ conf: __dirname + '/default.toml' });

Layered Configs

You can also use the app.setup to add a given configuration file or object on top of the current one as follows:

1app.setup('/path/to/settings.toml');
2
3app.setup('/path/to/settings.yaml');
4
5app.setup({ key: 'value' });
6
7app.setup({ key: 'new-value', foo: 'bar' });

Layering is useful, for example, to keep a default settings file in your server source code to be overwritten by your user's.

Logging

Nodecaf logs events to stdout by default where each line of the ouput is a JSON object. The log entries will have some default predefined values like pid, hostname etc... In your route handlers, use the functions available in the log object as follows:

1function({ log }){
2    log.info('hi');
3    log.warn({ lang: 'fr' }, 'au revoir');
4    log.fatal({ err: new Error() }, 'The error code is %d', 1234);
5}

Below is described the signature of the available logging methods.

• Method Name: one of the available log levels (debug, info, warn, error, fatal)
• First argument (optional): An object whose keys will be injected in the final entry.
• Second argument: A message to be the main line of the log. May contain printf-like replacements (%d, %s...)
• Remaning arguments: Will be inserted into the message (printf-like)

Nodecaf will automatically log some useful server events as described in the table below:

Type	Level	Event
error after headers sent	warn	An error happened inside a route after the headers were already sent
route	error	An error happened inside a route and was not caught
crash	fatal	An error happened that crashed the server process
request	debug	A request has arrived
response	debug	A response has been sent
app	debug	The application is starting up
app	info	The application has started
app	info	The application has stopped
app	info	The application configuration has been reloaded
event	warn	Called res.end() after response was already finished

Additionally, you can filter log entries by level and type with the following settings:

1[log]
2level = 'warn' # Only produce log entries with level 'warn' or higher ('error' & 'fatal')
3type = 'my-type' # Only produce log entries with type matching exactly 'my-type'

You can disable logging entirely for a given app by setting it to false in the config

1log = false

Async Handlers

Nodecaf accepts async functions as well as regular functions as route handlers. All rejections/error within your async handler will be gracefully handled. You will be able to avoid callback hell without creating bogus adapters for your promises.

1get('/my/thing', function({ res }){
2    res.end('My regular function works!');
3})
4
5get('/my/other/thing', async function({ res }){
6    await myAsyncThing();
7    res.end('My async function works too!');s
8})

Error Handling

In Nodecaf, any uncaught synchronous error happening inside route handler will be automatically converted into a harmless RESTful 500.

1post('/my/thing', function(){
2    throw new Error('Should respond with a 500');
3})

To support the callback error pattern, use the res.error() function arg.

1const fs = require('fs');
2
3post('/my/thing', function({ res }){
4    fs.readFile('./my/file', 'utf8', function(err, contents){
5        if(err)
6            return res.error(err);
7        res.end(contents);
8    });
9})

To use other HTTP status codes you can send an integer in the first parameter of res.error().

1post('/my/thing', function({ error }){
2    try{
3        doThing();
4    }
5    catch(e){
6        error(404, 'Optional message for the response');
7    }
8})

REST Assertions

Nodecaf provides you with an assertion module containing functions to generate the most common REST outputs based on some condition. Check an example to trigger a 404 in case a database record doesn't exist.

1get('/my/thing/:id', function({ params, db, res }){
2    let thing = await db.getById(params.id);
3    res.notFound(!thing, 'thing not found');
4
5    doStuff();
6})

If the record is not found, the res.notfound() call will stop the route execution right away and generate a RESTful NotFound error.

Along with notFound, the following assertions with similar behavior are provided:

Method	Status Code
badRequest	400
unauthorized	401
forbidden	403
notFound	404
conflict	409
gone	410
badType	415

Expose Globals

Nodecaf makes it simple to share global objects (eg.: database connections, instanced libraries) across all route handlers. In your lib/main.js you can expose an object of which all keys will become handler args.

1module.exports = () => new Nodecaf({
2    startup({ global }){
3        global.db = myDbConnection;
4        global.libX = new LibXInstance();
5    }
6});

Then in all routes you can:

1get('/my/thing', function({ db, libX }){
2    // use your global stuff
3})

CORS

Nodecaf provides a setting to enable permissive CORS on all routes. Defaults to disabled. In your conf file:

1cors = true
2cors = 'my://origin'
3cors = [ 'my://origin1', 'my://origin2' ]

Setup the cors according to the popular CORS Express middleware.

Handling Websocket

Use the websocket handler argument to expect a Websocket upgrade.

1get('/my/ws/endpoint', async ({ websocket }) => {
2
3    // Wait till ws connection is open
4    const ws = await websocket();
5
6    ws.on('message', m => {
7        ws.send('Hello World!');
8        ws.close();
9    });
10})

Other Settings

Property	Type	Description	Default
app.conf.delay	Integer	Milliseconds to wait before actually starting the app	0
app.conf.port	Integer	Port for the web server to listen (also exposed as user conf)	80 or 443
app.conf.cookie.secret	String	A secure random string to be used for signing cookies	none
opts.name	String	Manually set application name used in various places	package.jsons
opts.version	String	Manually set application version	package.jsons
opts.shouldParseBody	Boolean	Wether supported request body types should be parsed	true