Releases: optimizely/javascript-sdk
Releases · optimizely/javascript-sdk
Release 4.8.0-beta
[4.8.0-beta] - October 18, 2021
New Features
- Added a Lite bundle which does not include Data file manager and Event Processor packages. This reduces the bundle size up to 20% and is helpful for some platforms (such as edge service providers) that do not need extended functionality offered by these packages.
Performance Improvements
- Reduced SDK client initialization time by removing
OptimizelyConfigcreation from initialization. TheOptimizelyConfigobject is now created on the first call togetOptimizelyConfigAPI. - Made Improvements to logging mechanism. The SDK now no longer concatenates and formats messages which do not qualify for the log level set by the user.
Release 4.7.0
[4.7.0] - September 15, 2021
New Features
- Added new public properties to
OptimizelyConfig(#683, #698):- sdkKey
- environmentKey
- attributes
- audiences
- events
- experimentRules and deliveryRules to
OptimizelyFeature - audiences to
OptimizelyExperiment
- For details, refer to our documentation page:
Bug fixes
- Followed experimentIds order of experiments inside featuresMap of OptimizelyConfig (#701)
Deprecated
OptimizelyFeature.experimentsMapofOptimizelyConfigis deprecated as of this release. Please useOptimizelyFeature.experimentRulesandOptimizelyFeature.deliveryRules(#698)
Release 4.6.2
[4.6.2] - July 15, 2021
Bug fixes
- Fixed incorrect impression event payload in projects containing multiple flags with duplicate key rules (#690)
Release 4.6.1
[4.6.1] - July 8, 2021
Bug fixes
- Bumped
event-processorpackages to version0.8.2 - Fixed serving incorrect variation issue in projects containing multiple flags with same key rules (#687)
Release 4.6.0
[4.6.0] - May 27, 2021
New Features
- Added support for multiple concurrent prioritized experiments per flag (#664)
Bug fixes
- Fixed the issue of forced-variation and whitelist not working properly with exclusion group experiments (#664)
- Bumped
datafile-managerandevent-processorpackages to version0.8.1
Release 4.5.1
[4.5.1] - March 2, 2021
Bug fixes
- Refactored TypeScript type definitions to have
OptimizelyUserContextandOptimizelyDecisionimported fromshared_typesto provide isolation from internal modules (#655)
Release 4.5.0
[4.5.0] - February 17, 2021
New Features
-
Introducing a new primary interface for retrieving feature flag status, configuration and associated experiment decisions for users (#632, #634, #635, #636, #640, #642, #643, #644, #647, #648). The new
OptimizelyUserContextclass is instantiated withcreateUserContextand exposes the following APIs to getOptimizelyDecision:- setAttribute
- decide
- decideAll
- decideForKeys
- trackEvent
-
For details, refer to our documentation page:
Release 4.5.0-beta
[4.5.0-beta] - February 10, 2021
New Features
-
Introducing a new primary interface for retrieving feature flag status, configuration and associated experiment decisions for users (#632, #634, #635, #636, #640, #642, #643, #644, #647, #648). The new
OptimizelyUserContextclass is instantiated withcreateUserContextand exposes the following APIs to getOptimizelyDecision:- setAttribute
- decide
- decideAll
- decideForKeys
- trackEvent
-
For details, refer to our documentation page:
Release 4.4.3
[4.4.3] - November 23, 2020
Bug fixes
- Refactored TypeScript type definitions to have
OptimizelyOptionsimported fromshared_typesto provide isolation from internal modules (#629)
Release 4.4.2
[4.4.2] - November 19, 2020
Bug fixes
- In
Optimizelyclass, useanytype when assigning the return value ofsetTimeout. This is to allow it to type check regardless of whether it uses the browser or Node version ofsetTimeout(PR #623), (Issue #622) - Allowed to pass string type
logLeveltocreateInstance(PR #627), (Issue #614) - Excluded
suppressImplicitAnyIndexErrorsfrom TSconfig and resolved reported TS compiler issues (PR #616), (Issue #613) - Refactored TypeScript type definitions to only import from
shared_typesto provide isolation from internal modules (#625)
New Features
- Added
enabledfield to decision metadata structure to support upcoming application-controlled introduction of tracking for non-experiment Flag decisions (#619)