You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,10 @@
2
2
3
3
All notable changes to the LaunchDarkly client-side JavaScript SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
4
4
5
+
## [1.0.6] - 2016-08-23
6
+
### Changed
7
+
- Added check for EventSource before trying to connect Stream.
8
+
5
9
## [1.0.5] - 2016-08-22
6
10
### Changed
7
11
- Fixed an error that occurred on `hashchage`/`popstate` if the account had no goals.
Copy file name to clipboardExpand all lines: README.md
+17-4Lines changed: 17 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,19 @@ This is the official LaunchDarkly client-side JavaScript SDK. This SDK does two
7
7
* Makes feature flags available to your client-side (front-end) JavaScript code.
8
8
* Sends click, pageview, and custom events from your front-end for A/B tests and analytics.
9
9
10
+
## Browser Support
11
+
12
+
The LaunchDarkly client-side JavaScript SDK supports the following browsers:
13
+
14
+
* Chrome (any recent)
15
+
* Firefox (any recent)
16
+
* Safari (any recent)*
17
+
* Internet Explorer (IE10+)*
18
+
* Edge (any recent)*
19
+
* Opera (any recent)*
20
+
21
+
\* These browsers do not support streaming new flags to connected clients, even when `client.on('change')` is called.
22
+
10
23
## Installation
11
24
12
25
There are two ways to install the client-side SDK:
@@ -51,7 +64,7 @@ Out of the box, initializing the client will make a remote request to LaunchDark
51
64
52
65
Bootstrapping refers to providing the LaunchDarkly client object with an initial, immediately available set of feature flag values so that on page load `variation` can be called with no delay.
53
66
54
-
#### From the server-side SDK
67
+
#### From the server-side SDK
55
68
56
69
The preferred approach to bootstrapping is to populate the bootstrap values (a map of feature flag keys to flag values) from your backend. LaunchDarkly's server-side SDKs have a function called `all_flags`-- this function provides the initial set of bootstrap values. You can then provide these values to your front-end as a template. Depending on your templating language, this might look something like this:
57
70
@@ -66,15 +79,15 @@ If you bootstrap from the server-side, feature flags will be ready immediately,
66
79
67
80
#### From Local Storage
68
81
69
-
Alternatively, you can bootstrap feature flags from local storage.
82
+
Alternatively, you can bootstrap feature flags from local storage.
70
83
71
84
var client = LDClient.initialize('YOUR_ENVIRONMENT_ID', user, options = {
72
85
bootstrap: 'localStorage'
73
86
});
74
87
75
-
When using local storage, the client will store the latest flag settings in local storage. On page load, the previous settings will be used and the 'ready' event will be emitted immediately. This means that on page load, the user may see cached flag values until the next page load.
88
+
When using local storage, the client will store the latest flag settings in local storage. On page load, the previous settings will be used and the 'ready' event will be emitted immediately. This means that on page load, the user may see cached flag values until the next page load.
76
89
77
-
You can still subscribe to flag changes if you're using local storage.
90
+
You can still subscribe to flag changes if you're using local storage.
0 commit comments