• CORE-SERVER
  • Release
  • Databases
    • Redis
    • Rethinkdb
  • Constants
  • Tools
  • ENV
  • Pre-release

Tools shared between our backend services

npm version patch|minor|major && git push && git push --tags

import * as coreServer from '@amplement/core-server'

Databases related tools.

Redis doc

Rethinkdb doc

Constants doc

Tools doc

Environment variable handled.

• SENTRY_START_ERROR_CODE: optional to prevent reporting of errors under a particular status code (default: "500")
• DEBUG_APP_NAME: optional the name to display in loggers (default: "app")
• DEBUG_LEVEL: required the debug level to limit logger verbosity
• NODE_INSTANCE_ID: optional instance id of the service using the core server
• NODE_ENV: optional environment to use

To be able to test the package in a service, you can publish pre-release packages, here's a how-to.

For instance, we are on an app version 1.4.23 Prepare the pre-release version according to the level you want (patch, minor, major).

npm version prepatch

The version will become: 1.4.24-0

Then, if you want to bump this version, do:

npm version prerelease

The version will become: 1.4.24-1

Don't change this when merging, it will be replaced automatically on the next step.

When everything has been merging correctly, you can bump the version.

npm version patch

The version will become: 1.4.24