Gathering detailed insights and metrics for @optimizely/optimizely-sdk
Gathering detailed insights and metrics for @optimizely/optimizely-sdk
Gathering detailed insights and metrics for @optimizely/optimizely-sdk
Gathering detailed insights and metrics for @optimizely/optimizely-sdk
JavaScript SDK for Optimizely Feature Experimentation and Optimizely Full Stack (legacy)
npm install @optimizely/optimizely-sdk
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
80 Stars
665 Commits
82 Forks
92 Watching
73 Branches
282 Contributors
Updated on 27 Nov 2024
TypeScript (52.02%)
JavaScript (47.98%)
Cumulative downloads
Total Downloads
Last day
-28.9%
36,765
Compared to previous day
Last week
-9.3%
225,717
Compared to previous week
Last month
1.2%
1,052,726
Compared to previous month
Last year
6.9%
11,768,861
Compared to previous year
5
47
This repository houses the JavaScript SDK for use with Optimizely Feature Experimentation and Optimizely Full Stack (legacy).
Optimizely Feature Experimentation is an A/B testing and feature management tool for product development teams that enables you to experiment at every step. Using Optimizely Feature Experimentation allows for every feature on your roadmap to be an opportunity to discover hidden insights. Learn more at Optimizely.com, or see the developer documentation.
Optimizely Rollouts is free feature flags for development teams. You can easily roll out and roll back features in any application without code deploys, mitigating risk for every feature on your roadmap.
For Browser applications, refer to the JavaScript SDK's developer documentation for detailed instructions on getting started with using the SDK within client-side applications.
For Node.js applications, refer to the JavaScript (Node) variant of the developer documentation.
For Edge Functions, we provide starter kits that utilize the Optimizely JavaScript SDK for the following platforms:
Note: We recommend using the Lite version of the sdk for edge platforms. These starter kits also use the Lite variant of the JavaScript SDK which excludes the datafile manager and event processor packages.
Ensure the SDK supports all of the platforms you're targeting. In particular, the SDK targets modern ES5-compliant JavaScript environment. We officially support:
npm test
to validate for yourself), but are not formally supported.In addition, other environments are likely compatible but are not formally supported including:
JavaScript (Browser): Modern web browser that is ES5-compliant.
JavaScript (Node): Node 16.0.0+
Once you've validated that the SDK supports the platforms you're targeting, fetch the package from NPM:
Using npm
:
1npm install --save @optimizely/optimizely-sdk
Using yarn
:
1yarn add @optimizely/optimizely-sdk
Using pnpm
:
1pnpm add @optimizely/optimizely-sdk
Using deno
(no installation required):
1import optimizely from "npm:@optimizely/optimizely-sdk"
See the Optimizely Feature Experimentation developer documentation for JavaScript (Browser) to learn how to set up your first JavaScript project and use the SDK for client-side applications.
The package has different entry points for different environments. The browser entry point is an ES module, which can be used with an appropriate bundler like Webpack or Rollup. Additionally, for ease of use during initial evaluations you can include a standalone umd bundle of the SDK in your web page by fetching it from unpkg:
1<script src="https://unpkg.com/@optimizely/optimizely-sdk/dist/optimizely.browser.umd.min.js"></script> 2 3<!-- You can also use the unminified version if necessary --> 4<script src="https://unpkg.com/@optimizely/optimizely-sdk/dist/optimizely.browser.umd.js"></script>
When evaluated, that bundle assigns the SDK's exports to window.optimizelySdk
. If you wish to use the asset locally (for example, if unpkg is down), you can find it in your local copy of the package at dist/optimizely.browser.umd.min.js. We do not recommend using this method in production settings as it introduces a third-party performance dependency.
As window.optimizelySdk
should be a global variable at this point, you can continue to use it like so:
1const optimizelyClient = window.optimizelySdk.createInstance({ 2 sdkKey: '<YOUR_SDK_KEY>', 3 // datafile: window.optimizelyDatafile, 4 // etc. 5}); 6 7optimizelyClient.onReady().then(({ success, reason }) => { 8 if (success) { 9 // Create the Optimizely user context, make decisions, and more here! 10 } 11});
Regarding EventDispatcher
s: In Node.js and browser environments, the default EventDispatcher
is powered by the http/s
modules and by XMLHttpRequest
, respectively. In all other environments, you must supply your own EventDispatcher
.
See the Optimizely Feature Experimentation developer documentation for JavaScript (Node) to learn how to set up your first JavaScript project and use the SDK for server-side applications.
The package has different entry points for different environments. The node entry point is CommonJS module.
1const optimizelySdk = require('@optimizely/optimizely-sdk'); 2 3const optimizelyClient = optimizelySdk.createInstance({ 4 sdkKey: '<YOUR_SDK_KEY>', 5 // datafile: window.optimizelyDatafile, 6 // etc. 7}); 8 9optimizelyClient.onReady().then(({ success, reason }) => { 10 if (success) { 11 // Create the Optimizely user context, make decisions, and more here! 12 } 13});
Regarding EventDispatcher
s: In Node.js environment, the default EventDispatcher
is powered by the http/s
module.
There is a mix of testing paradigms used within the JavaScript SDK which include Mocha, Chai, Karma, and Jest, indicated by their respective *.tests.js
and *.spec.ts
filenames.
When contributing code to the SDK, aim to keep the percentage of code test coverage at the current level () or above.
To run unit tests on the primary JavaScript SDK package source code, you can take the following steps:
~/javascript-sdk/packages/optimizely-sdk
directory.npm install
to install all project dependencies.npm test
to run all test files.npm run test-xbrowser
to run tests in many browsers via BrowserStack.This information is relevant only if you plan on contributing to the SDK itself.
1# Prerequisite: Install dependencies. 2npm install 3 4# Run unit tests. 5npm test 6 7# Run unit tests in many browsers, currently via BrowserStack. 8# For this to work, the following environment variables must be set: 9# - BROWSER_STACK_USERNAME 10# - BROWSER_STACK_PASSWORD 11npm run test-xbrowser
/.github/workflows/javascript.yml contains the definitions for BROWSER_STACK_USERNAME
and BROWSER_STACK_ACCESS_KEY
used in the GitHub Actions CI pipeline. When developing locally, you must provide your own credentials in order to run npm run test-xbrowser
. You can register for an account for free on the BrowserStack official website here.
For more information regarding contributing to the Optimizely JavaScript SDK, please read Contributing.
This version represents a major version change and, as such, introduces some breaking changes. Please refer to the Changelog for more details.
To access the Feature Management configuration in the Optimizely dashboard, please contact your Optimizely customer success manager.
@optimizely/optimizely-sdk
is developed and maintained by Optimizely and many contributors. If you're interested in learning more about what Optimizely Feature Experimentation can do for your company you can visit the official Optimizely Feature Experimentation product page here to learn more.
First-party code (under packages/optimizely-sdk/lib/
, packages/datafile-manager/lib
, packages/datafile-manager/src
, packages/datafile-manager/__test__
, packages/event-processor/src
, packages/event-processor/__tests__
, packages/logging/src
, packages/logging/__tests__
, packages/utils/src
, packages/utils/__tests__
) is copyright Optimizely, Inc. and contributors, licensed under Apache 2.0.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
11 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More