v5.0.0

This version does not have any breaking changes. It's a major version as it has an automatic migration-step for the encryptionKey option. So if you're using that option, please continue reading.

Short story, Node.js deprecated the below APIs and we had to do encryption differently. Conf should be able to read both the new and old encryption format and it will write the new encryption format if you change any config. The migration is fully automatic, but please test your app thoroughly in case there are any issues.

• Replace deprecated crypto.createDecipher() and crypto.createCipher() Node.js methods (#76) 177fe65

v4.1.0...v5.0.0

v4.1.0

• Add accessPropertiesByDotNotation option (#67) 94f71c5
• Add .onDidAnyChange method (#66) 0c942e1

v4.0.2...v4.1.0

v4.0.2

• TypeScript - Fix parameter name order for onDidChange callback (#70) 201c2ff

v4.0.1...v4.0.2

v4.0.1

• TypeScript - Fix return type of onDidChange (#65) 2bda368

v4.0.0...v4.0.1

v4.0.0

Breaking

• The config is now stored in %APPDATA% instead of %LOCALAPPDATA% on Windows, which is more correct. There's unfortunately no automatic migration path. To continue using the old config location, run npm i 'env-paths@^1.0.0' and set the cwd option:

   const Conf = require('conf');
   const envPaths = require('env-paths');
   
   const config = new Conf({
   	cwd: envPaths('<projectName>', {suffix: 'nodejs'}).config
   });

• For TypeScript users only: Refactor TypeScript definition to CommonJS compatible export (#64) 277d70a
  - You need to change import Conf from 'conf'; to import Conf = require('conf');

Enhancements

• Add support for JSON schema (#58) 373afb9
• Fix path derivation logic (#62) bb26c4f

---

v3.0.0...v4.0.0

v3.0.0

Breaking:

• Require Node.js 8 e30cdad
• Prevent unsupported JSON values d162504

Enhancements:

• Add TypeScript definition (#61) 330e011
• Add clearInvalidConfig option d725709
• Add serialize and deserialize options (#59) e18a4a3

v2.2.0...v3.0.0

v2.1.0

• Allow extension-less config filename f1f1c59