This module provides a quick and easy way to create powerful http servers.
npm install impulse-api
npm run test
A at least one .js file must exist at {project-root}/routes in order to initialize a new Api. See sample-routes for reference.
const Impulse = require('impulse-api');
const config = {
env: 'DEV',
port: 3000,
secretKey: 'topSecret!',
appKey: '@adminSecretKey',
version: '1.0.0',
name: 'Hello-World-Api',
routeDir: __dirname.concat('/routes'),
services: {}
}
const api = new Impulse(config);
api.init().then((response) => {
console.log(response)
}).catch((error) => {
console.log(error)
})-env (required)
The Environment the server should be running in. Typically this can be parsed from .env or hoisted from process.ENV.
-port (required) The port on which the server should be running.
-secretKey The key used for all JSON web token encoding and decoding.
-applicationKey The key used for all basic application authentication.
-name The name of the server.
-version The version of the server.
-routeDir (required) The location of the root route directory.
-services Optional object that is available on every route. Services is ideal for storing connection information to databases or any other auxiliary functionality.
By default, all Impulse-APIs have a /heartbeat endpoint that returns 200 along with the following standard output:
{ status: 'alive' }Routes are functions that expose HTTP path functionality.
Route files must exist in any number of folders or subfolders at {project-root}/routes
// routes/documents.js
exports.getDocument = {
name: 'getDocument',
description: 'get a document by id',
method: 'get',
endpoint: '/api/document/:id',
version: 'v1',
tokenAuth: true,
inputs: {
id: {
required: true,
validate: val => parseInt(val, 10)
},
},
run: (services, inputs, next) => {
const id = inputs.id;
next(200, {
id
});
},
};Impulse-Api comes with JSON web token auth built in. As long as secretKey is provided to the server configuration on initialization, routes can use an optional tokenAuth:true in order to enable basic JWT authentication.
Additionally, any variables that are encoded in the token are accessible once the token has been decoded via inputs.decoded.
Token generation is handled via Impulse.Auth which again utilizes the JSON web token package.
const { Auth } = require('impulse-api');
{ decode: [Function],
verify: [Function],
sign: [Function],
JsonWebTokenError: [Function: JsonWebTokenError],
NotBeforeError: [Function: NotBeforeError],
TokenExpiredError: [Function: TokenExpiredError] }For admin type routes, Impulse-Api also provides applicationAuth which secures any routes behind basic key authorization provided by appKey in the server configuration. The applicationAuth can be verified and passed in the header, parameters, query, or body as key.
// routes/users.js
exports.createUser = {
name: 'createUser',
description: 'create a new user',
method: 'post',
endpoint: '/api/user/',
version: 'v1',
applicationAuth: true,
inputs: {
username: {
required: true,
},
password: {
required: true,
}
},
run: (services, inputs, next) => {
const id = inputs.id;
next(200, {
id
});
},
};If a route specifies both Application and Token auth, Application auth will take precedence.
-- Application auth routes should not be called from any public client since this will expose appKey.
Impulse-Api automatically parses all request query, body, params, and files variables with the following priority: query, body, params, files. Header fields are always parsed.
This allows for very dynamic routes. The following routes will all parse newEmailAddress.
PUT /user/:id/&newEmailAddress=hello@world.com
PUT /user/:id/
body: {
newEmailAddress: 'hello@world.com'
}
PUT /user/:id/
json: {
"newEmailAddress": "hello@world.com"
}
PUT /user/:id/
params: newEmailAddress="hello@world.com"