🐛 Fixed

• With autopoll initial tryReadFromCache takes 5 seconds #43

🚀 Added

• Local Flag Overrides

🐛 Bug fix

• Fixing CONTAINS and NOT CONTAINS operator issues (https://github.com/configcat/js-sdk/issues/51)

🚀 Features

• Introduce new log level into IConfigCatLogger interface: Debug

🛡 Security

• update dependencies (follow-redirects , engine.io , ansi-regex, log4js)

Optional custom property fix.

• .dispose() fix: #36
• Lazy loading concurrency fix
• Auto polling initialization fix

Support async cache implementations too.

Updating dependencies.

Updating dependencies including configcat-common.

🛡 Security updates

• Update dependecies
• Remove IConfigFetcher type re-export (PR #31)

• Remove accidentally included GitHub action file from release package.

🐛 Fixed

• Fixed a wrong behaviour that resulted in unintended calls on the AutoPoll's onConfigChanged callback even when the HTTP fetch failed.

v5.4.0

🚀 Features

• Introduce new function getAllValues - returns all values of a feature flag or setting

v5.3.2

🐛 Bug Fixes

• FIX: Cache optimization

v5.3.1

🐛 Bug Fixes

• FIX: Type error when ProjectConfig changed

v5.3.0

🚀 Features

• Introduce new config parameter - maxInitWaitTimeSeconds - Maximum waiting time between the client initialization and the first config acquisition in seconds.

Exporting DataGovernance const

Update common-js to fix the baseUrl redirect flow

Addressing global data handling and processing trends via Data Governance feature. Customers can control the geographic location where their config JSONs get published to. See the docs.

We are introducing a new DataGovernance initialization parameter. Set this parameter to be in sync with the Data Governance preference on the Dashboard.

Breaking change:

• Custom cache implementations should implement the new cache interface using key parameter in the get/set methods.

fix issue#6, issue#12

Support ES module

Turned on declarationMap in tsconfig.json