Releases: optimizely/javascript-sdk
Releases · optimizely/javascript-sdk
Release 4.3.1
[4.3.1] - October 5, 2020
Bug fixes
- Exported
OptimizelyConfig
andUserAttributes
type in TypeScript type definitions (#587)
Release 4.3.0
Release 4.2.1
[4.2.1] - August 10, 2020
Bug fixes
- Remove incorrect warning about invalid variation ID when user not bucketed into experiment or feature rollout (#549)
Release 4.2.0
[4.2.0] - July 31, 2020
New Features
- Better offline support in React Native apps:
Bug fixes
- Fixed log messages for Targeted Rollouts (#515)
Release 4.1.0
[4.1.0] - July 7, 2020
New Features
- Added support for JSON feature variables: new methods
getFeatureVariableJSON
andgetAllFeatureVariables
(#467, #470) - Added support for authenticated datafiles when running in Node.js. Pass
datafileAccessToken
withindatafileOptions
to request an authenticated datafile using the token (#498, #502):const optimizelySDK = require('@optimizely/optimizely-sdk'); var optimizelyClientInstance = optimizely.createInstance({ sdkKey: '<Your SDK key>', datafileOptions: { datafileAccessToken: '<Your datafile access token>', } });
Bug fixes
Release 4.1.0-beta
[4.1.0-beta] - June 16, 2020
New Features
- Added support for JSON feature variables: new methods
getFeatureVariableJson
andgetAllFeatureVariables
(#467, #470) - Added support for authenticated datafiles when running in Node.js. Pass
datafileAccessToken
withindatafileOptions
to request an authenticated datafile using the token (#498, #502):const optimizelySDK = require('@optimizely/optimizely-sdk'); var optimizelyClientInstance = optimizely.createInstance({ sdkKey: '<Your SDK key>', datafileOptions: { datafileAccessToken: '<Your datafile access token>', } });
Bug fixes
- Fixed audience evaluation log level: changed from
INFO
toDEBUG
(#496)
Release 4.0.0
[4.0.0] - April 30, 2020
New Features
- Removed lodash dependency
- ES module entry point for the browser -
"module"
property ofpackage.json
points todist/optimizely.browser.es.min.js
(#445)
Breaking Changes
- Removed
Promise
polyfill from browser entry point (417). - Changed functionality of JSON schema validation in all entry points (442).
- Previously,
skipJSONValidation
flag was used by the user to specify whether the JSON object should be validated. - Now,
skipJSONValidation
has been removed entirely from all entry points. Instead, a user will need to importjsonSchemaValidator
from@optimizely/optimizely-sdk/dist/optimizely.json_schema_validator.min.js
and pass it tocreateInstance
to perform validation as shown below:
const optimizelySDK = require('@optimizely/optimizely-sdk'); const jsonSchemaValidator = require('@optimizely/optimizely-sdk/dist/optimizely.json_schema_validator.min'); // Require JSON schema validation for the datafile var optimizelyClientInstance = optimizely.createInstance({ datafile: datafile, jsonSchemaValidator: jsonSchemaValidator, });
- Previously,
- Dropped support for Node.js version <8 (#456)
Bug fixes
Release 4.0.0-rc.2
[4.0.0-rc.2] - April 24, 2020
Bug fixes
- Allow multiple instances to be created from the same datafile object (#462)
Release 4.0.0-rc.1
[4.0.0-rc.1] - April 17, 2020
New Features
- ES module entry point for the browser -
"module"
property ofpackage.json
points todist/optimizely.browser.es.min.js
(#445)
Breaking Changes:
- Dropped support for Node.js version <8 (#456)
Bug fixes
- Node.js datafile manager uses gzip,deflate compression for requests (#456)
Release 4.0.0-alpha.1
[4.0.0-alpha.1] - April 2, 2020
Breaking Changes:
- Removed
Promise
polyfill from browser entry point (417)