This is a simple fasitfy application skeleton for JSON API server with some pre-defined features.
After calling the default exported function, the fastify server will listen on the specified host and port. The returned value of the function is a fastify instance. By default, this instance will also be registered to the global scope with variable name app
. You can access it via global.app
or just app
. This name can be changed by setting the app.globalAppVariable
in the config. To prevent this behavior, set the app.disableGlobalAppVariable
to true
.
Reply helpers
There are some useful helpers can be used in the route handler. In the following example, the req
is the first parameter of the handler, also know as request
. The res
is the second parameter of the handler function, also known as the reply
object in fastify.
Send a 200 response with the data and meta object.
Can be disabled by setting the app.disableReplyHelperFunctions
to true
.
res.ok({ok: 'It works!'}, {addition: 'someValue'})
{
"status": "ok",
"data": {
"ok": "It works!"
},
"meta": {
"addition": "someValue"
}
}
Send an error object to the client with message and code. The HTTP status code will be set to statusCode(defaults to 200).
Can be disabled by setting the app.disableApiErrorHandler
to true
.
throw new ApiError('User Not found', 'err_code_user_not_found', 404)
will return with http status code 404:
{
"status": "error",
"message": "User Not found",
"code": "err_code_user_not_found"
}
By default, some endpoints for health checking are registered. This behavior can be disabled by setting the app.disableHealthCheckRoutes
to true
.
The prefix of these endpoints can be changed by setting the app.healthCheckRoutesPrefix
in the config.
For health checking.
Generate an api error response with the code passed in the query string.
Generate an uncaught error response.
If the database
section is set in the config, it will also connect to the database using the knex
package. The initialized knex instance will be stored in the global.knex
variable in the process scope.
The config object passed to the default exported function can be accessed via app.config
By default, a state
object will be registered to the request object by using fastify.decorateRequest
. This behavior can be disabled by setting the app.disableAddRequestState
to true
.
By default, the server will add the CORS headers to the response. This behavior can be disabled by setting the app.disableCors
to true
.
By default, the server will log the request and response to console. This behavior can be disabled by setting the fastify.disableRequestLogging
to true
, or by setting the fastify.logger
. All the settings under the fastify
key will be passed to the fastify
construct function.
By default, the server will log the request body and headers. These behaviors can be disabled by setting the app.disableLogRequestBody
or app.disableLogRequestHeaders
to true
.
By default, the server will send a Request-Id
header to the client. This behavior can be disabled by setting the app.disableSendRequestIdHeader
to true
.
By default, if ApiError(message, code, statusCode)
is not caught by local error handler, the server will handle this ApiError and return the error object to the client, with HTTP status code statusCode
which defaults to 200
.
The response format is:
{
"status": "error",
"message": "custom error messsage string or object",
"code": "custom error code"
}
This behavior can be disabled by setting the app.disableApiErrorHandler
to true
.
By default, the server will handle the uncaught errors and return the error object to the client. The HTTP status code defaults to 200 which also can be changed by settting app.InternalServerErrorCode
. If process.env.NODE_ENV === 'development'
, the error detail will be sent to the client.
The response format is:
{
"status": "error",
"message": "Internal Server Error"
}
This handler can be disabled by setting the app.disableApiErrorHandler
to true
.
By default, the server will log the API error(throw new ApiError()
). This behavior can be disabled by setting the app.disableLogApiError
to true
.
You can organize your API by putting them in different folders. The folder name will be the prefix of the API. For example, if you have an app/user/api.js
file, you can access it via http://localhost:port/user/YOUR-API
. Only the file with the api.js
will be registered as fastify plugin.
npm install fastify-app js-yaml
Note
The
js-yaml
can be omitted if you don't want to use a yaml config file.
Create a config.yaml
file in your project root with the following example:
server:
host: 0.0.0.0
port: 53004
fastify:
disableRequestLogging: false
bodyLimit: 52428800 #in bytes, 50Mb
logger:
redact:
- "req.headers.authorization"
app:
globalAppVariable: app
disableCors: false
disableLogRequestBody: false
disableLogRequestHeaders: false
disableSendRequestIdHeader: false
disableApiErrorHandler: false
internalServerErrorCode: 200
disableHealthCheckRoutes: false
healthCheckRoutesPrefix: "/health-check"
enableHealthCheckShowsGitRev: false
disableAddRequestState: false
disableLogApiError: false
disableReplyHelperFunctions: false
database:
client: mysql2
mysql2:
host: 127.0.0.1
port: 3306
database: test
user: dbuser
password: dbpass
timezone: +08:00
pg:
host: localhost
port: 5432
user: dbuser
password: dbpass
database: test
schema: public
timezone: Asia/Shanghai
ssl: true
pool:
min: 1
max: 20
idleTimeoutMillis: 60000
If you don't want this package to connect to a database, just remove the
database
section from the config.
Create an app
folder in your project root, and create an api.js
file in it with the following content:
'use strict';
module.exports = function() {
// Put custom code here, runs before fastify initializing.
// your custom code
// then return your plugin function to the fastify register.
return plugin
}
function plugin(fastify, opts, done) {
fastify.get('/ok', async function(req, res) {
return res.ok({
ok: 'It works!',
})
})
done()
}
After starting the server, this API endpoint can be accssed via http://host:port/ok
.
You can also create subfolders in the app
folder to organize your API. If you have an app/user/api.js
file, you can access it via http://localhost:port/user/YOUR-API
.
require('fastify-app')(require('js-yaml').load(require('fs').readFileSync('./config.yaml', 'utf8')))