Bump ldclient-js from 1.7.4 to 2.10.2

[dependabot-preview]

Bumps ldclient-js from 1.7.4 to 2.10.2.

Release notes

Sourced from ldclient-js's releases.

2.10.2

[2.10.2] - 2019-05-01

Fixed:

• Fixed a problem that prevented the Electron and client-side Node SDKs from reporting their own version strings correctly. This fix does not affect the browser JS SDK, so there is no need to upgrade if you are using that.

Note on future releases:

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now js-client-sdk rather than js-client.

The package names will also change. In the 2.10.2 release, there were packages for ldclient-js, ldclient-react and ldclient-js-common; in all future releases, they will be launchdarkly-js-client-sdk, launchdarkly-react-client-sdk, and launchdarkly-js-sdk-common, respectively.

2.10.1

[2.10.1] - 2019-04-23

Fixed:

• The 2.10.0 release added a usage of the Promise.finally() method, which made it incompatible with some older browsers. This has been removed. (#151)

2.10.0

[2.10.0] - 2019-04-19

Added:

• Generated TypeDoc documentation for all types, properties, and methods is now available online at https://launchdarkly.github.io/js-client-sdk/. Currently this will only be for the latest released version.
• The SDK now allows you to specify an anonymous user without a key (i.e. the anonymous property is true, and there is no key property). In that case, the SDK will generate a UUID and send that as the user key. It will also cache this generated key in local storage (if local storage is available) so that anonymous users in the same browser will always get the same key.

Fixed:

• Setting user attributes to non-string values when a string was expected would prevent evaluations and analytics events from working. The SDK will now convert attribute values to strings as needed.

2.9.7

[2.9.7] - 2019-04-16

Fixed:

• If there are pending analytics events when the page is being closed, the SDK normally attempts to deliver them by making a synchronous HTTP request. Chrome, as of version 73, does not allow this and logs an error. An upcoming release will change how events are sent, but as a temporary measure to avoid these errors, the SDK will now simply discard any pending events when the page is being closed if the browser is Chrome version 73 or higher. In other browsers, there is no change. Note that this means that in Chrome 73, some events may be lost; that was already the case. The purpose of this patch is simply to avoid triggering errors. (#178)

(The 2.9.6 release was an error and has been removed.)

2.9.5

[2.9.5] - 2019-03-12

Fixed:

• In React, when using the bootstrap property to preload the SDK client with flag values, the client will now become ready immediately and make the flags available to other components as soon as it is initialized; previously this did not happen until after componentDidMount.
• The user attribute secondary was not included in the TypeScript declarations and therefore could not be used from TypeScript code.

2.9.4

[2.9.4] - 2019-02-22

Fixed:

• Running inside an iframe on Chrome with third-party cookies disabled-- which also disables HTML5 local storage-- would cause a security exception (due to the SDK attempting to check whether window.localStorage exists). This was a long-standing problem, but became worse in the 2.9.0 release since the SDK now checks for browser capabilities like this regardless of whether you've attempted to use them yet. It should now simply log a warning if you try to use bootstrap: "localstorage" when local storage is disabled. (#138)
• If the SDK received streaming updates out of order (rare, but possible) such that it received "flag X was deleted" prior to "flag X was created", an uncaught exception would be logged in the browser console (but would not otherwise affect anything).
• A supported user property, privateAttributeNames, was not usable from TypeScript because it was omitted from the TypeScript declarations.
• Several TypeScript declarations had been changed from interface to type. They all now use interface, except for LDFlagValue which is a type alias. This should not affect regular usage of the SDK in TypeScript, but it is easier to extend an interface than a type if desired.
• Removed a window message listener that was previously used for integration with the LaunchDarkly dashboard, but is no longer used.

2.9.3

[2.9.3] - 2019-02-12

Fixed:

... (truncated)

Changelog

Sourced from ldclient-js's changelog.

[2.10.2] - 2019-05-01

Fixed:

• Fixed a problem that prevented the Electron and client-side Node SDKs from reporting their own version strings correctly. This fix does not affect the browser JS SDK, so there is no need to upgrade if you are using that.

Note on future releases:

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now js-client-sdk rather than js-client.

The package names will also change. In the 2.10.2 release, there were packages for ldclient-js, ldclient-react and ldclient-js-common; in all future releases, they will be launchdarkly-js-client-sdk, launchdarkly-react-client-sdk, and launchdarkly-js-sdk-common, respectively.

[2.10.1] - 2019-04-23

Fixed:

• The 2.10.0 release added a usage of the Promise.finally() method, which made it incompatible with some older browsers. This has been removed. (#151)

[2.10.0] - 2019-04-19

Added:

• Generated TypeDoc documentation for all types, properties, and methods is now available online at https://launchdarkly.github.io/js-client/. Currently this will only be for the latest released version.
• The SDK now allows you to specify an anonymous user without a key (i.e. the anonymous property is true, and there is no key property). In that case, the SDK will generate a UUID and send that as the user key. It will also cache this generated key in local storage (if local storage is available) so that anonymous users in the same browser will always get the same key.

Fixed:

• Setting user attributes to non-string values when a string was expected would prevent evaluations and analytics events from working. The SDK will now convert attribute values to strings as needed.

[2.9.7] - 2019-04-16

Fixed:

• If there are pending analytics events when the page is being closed, the SDK normally attempts to deliver them by making a synchronous HTTP request. Chrome, as of version 73, does not allow this and logs an error. An upcoming release will change how events are sent, but as a temporary measure to avoid these errors, the SDK will now simply discard any pending events when the page is being closed if the browser is Chrome version 73 or higher. In other browsers, there is no change. Note that this means that in Chrome 73, some events may be lost; that was already the case. The purpose of this patch is simply to avoid triggering errors. (#178)

[2.9.6] - 2019-04-16

This release was an error and has been removed.

[2.9.5] - 2019-03-12

Fixed:

• In React, when using the bootstrap property to preload the SDK client with flag values, the client will now become ready immediately and make the flags available to other components as soon as it is initialized; previously this did not happen until after componentDidMount.
• The user attribute secondary was not included in the TypeScript declarations and therefore could not be used from TypeScript code.

[2.9.4] - 2019-02-22

Fixed:

• Running inside an iframe on Chrome with third-party cookies disabled-- which also disables HTML5 local storage-- would cause a security exception (due to the SDK attempting to check whether window.localStorage exists). This was a long-standing problem, but became worse in the 2.9.0 release since the SDK now checks for browser capabilities like this regardless of whether you've attempted to use them yet. It should now simply log a warning if you try to use bootstrap: "localstorage" when local storage is disabled. (#138)
• If the SDK received streaming updates out of order (rare, but possible) such that it received "flag X was deleted" prior to "flag X was created", an uncaught exception would be logged in the browser console (but would not otherwise affect anything).
• A supported user property, privateAttributeNames, was not usable from TypeScript because it was omitted from the TypeScript declarations.
• Several TypeScript declarations had been changed from interface to type. They all now use interface, except for LDFlagValue which is a type alias. This should not affect regular usage of the SDK in TypeScript, but it is easier to extend an interface than a type if desired.
• Removed a window message listener that was previously used for integration with the LaunchDarkly dashboard, but is no longer used.

[2.9.3] - 2019-02-12

Fixed:

• The React SDK was pulling in the entire lodash package. This has been improved to only require the much smaller camelcase tool from lodash.
• The React SDK now lists React itself as a peer dependency rather than a regular dependency, so it will not included twice in an application that already requires React.
• Corrected the TypeScript declaration for the identify method to indicate that its asynchronous result type is LDFlagSet, not void. (Thanks, impressiver!)
• Corrected and expanded many documentation comments in the TypeScript declarations.

... (truncated)

Commits

• dab4f93 version 2.10.2
• 27d5b7e fix release script
• ddf9461 prepare 2.10.2 release (#153)
• e4831cd update CircleCI link
• 4b53c3e fix documentation link
• 0a3cb25 version 2.10.1
• f29ba84 prepare 2.10.1 release (#152)
• e7edb33 version 2.10.0
• a00682c prepare 2.10.0 release (#149)
• 73598dd fix broken readme links
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[jaredgalanis]

@dependabot rebase

[jaredgalanis]

Closing in favor of #133 since that updates the package to a more recent version.

[dependabot-preview]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.