KrakenJS config precedence across Express and Node compatibility boundaries
This question concerns kraken-js , the npm Express framework, rather than the Kraken cryptocurrency exchange API. The goal is to define how configuration should change when moving from base config/config.json to environment-specific files such as config/development.json or config/production.json , while remaining within the installed release’s declared Node
express
nodejs
krakenjs