A lean boilerplate application for building RESTful APIs (Microservice) in Node.js using hapi.js. Follows industry standard best practices, and uses latest async/await ES8 feature. Bring your own front-end. Plug-in your own Database.
|Uses latest ES8/ES2017 features (async/await)||Uses latest ES7 and ES8 features including async/await|
|Application Configuration via config||Node-config organizes hierarchical configurations for your app deployments. It lets you define a set of default parameters, and extend them for different deployment environments (development, qa, staging, production, etc.).|
|Auto Documentation via hapi-swagger||This will self document the API interface. You can also tests your APIs using the Swagger interface.|
|Unit and Integration Tests via Mocha with async/await||Demo unit and integration tests using latest ES7/ES8 features.|
|Code Coverage via istanbul||Supports code coverage of ES8 code using istanbul and mocha. Code coverage reports are saved in
|Logging via bunyan||Bunyan is simple and fast JSON logging library. Logs timestamp, machine name and process ID and most importantly makes it really easy to parse logs as it logs in JSON format. You can selectively turn on/off logs by setting log level via LOG_LEVEL env variable.|
|API parameter validation via joi||Validate body, params, query, headers and cookies of a request (via middleware) and return a response with errors; if any of the configured validation rules fail. You won't anymore need to make your route handler dirty with such validations.|
|Application monitoring via New Relic||Set
|Pre-commit hooks via husky||Runs lint and tests before any commit is made locally, making sure that only tested and quality code goes through|
|Uses nock for mocking http requests in integration tests||Nock is an HTTP mocking and expectations library. It can be used to test modules that perform HTTP requests in isolation.|
|Uses yarn over npm||Uses new released yarn package manager by facebook. You can read more about it here|
|Docker compatible||Docker and Docker Compose files to develop and deploy via Docker|
|Uses EditorConfig||EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs|
# Install dependencies $ yarn
# Start Server # Set environment variables defined in `config/custom-environment-variables.json` like `OPEN_WEATHER_API_KEY=xxx` $ yarn start
# Try GET /ping to make sure server is up $ curl http://localhost:3030/ping
# Run Tests $ yarn test
# copy sample.dev.env to dev.env $ cp bin/sample.dev.env bin/dev.env
# Start Server $ bash bin/development.sh
# copy sample.test.env to test.env $ cp bin/sample.test.env bin/test.env
# Run Tests $ bash bin/test.sh
config is used to configure application.
config/test/jsonfor test environment.
config/custom-environment-variablesis used to read values from environment variables. For ex. if
APP_PORTenv var is set it can be accessed as
config.get('app.port'). You can read more on custom environment variables here.
# Run lint yarn lint
bin/sample.dev.envin your own environment (AWS, Heroku etc) and
docker build -t hapi-starter-kit-oss .
docker run -d -p 3030:3030 --name hapi-starter-kit-oss hapi-starter-kit-oss
hapi-swaggerself documents all the APIs.
http://localhost:3030/documentationto access the documentation after starting the server.
good-consolein development environment, remove it from
Please feel free to open an issue if you can have any questions or trouble using this starter kit.
Contributions are all welcome and encouraged. For code contributions submit a pull request with unit test.
This project is licensed under the MIT License