Skip to content

Conversation

@eli-darkly
Copy link
Contributor

[2.5.0] - 2018-08-27

Changed:

  • Starting in version 2.0.0, there was a problem where analytics events would not be generated correctly if you initialized the client with bootstrap data, because the bootstrap data did not include some flag metadata that the front end uses for events. The client now supports an extended format for bootstrap data that fixes this problem; this is generated by calling a new method that has been added to the server-side SDKs, allFlagsState/all_flags_state (previously allFlags/all_flags). Therefore, if you want analytics event data and you are using bootstrap data from the back end, you should upgrade both your JavaScript SDK and your server-side SDK, and use allFlagsState on the back end. This does not require any changes in your JavaScript code. If you use bootstrap data in the old format, the SDK will still be usable but events will not work correctly.
  • When posting events to LaunchDarkly, if a request fails, it will be retried once.
  • The TypeScript mappings for the SDK were omitted from the distribution in the previous release. They are now in the distribution again, in the root folder instead of in src, and have been renamed from index.d.ts to typings.d.ts.

eli-darkly and others added 30 commits August 9, 2018 19:46
override jsdom version to avoid test problems
change identify() result back to a key-value map like it used to be
[ch22054] Document the Promise polyfill and make all polyfill sections consistent
…hed NPM package (#94)

TIL that `npm pack` will build the tarball that actually gets uploaded to the NPM servers.

If you want to verify this works,

```sh
  npm run clean
  npm run prepublishOnly # simulate build that occurs before publishing
  npm pack # generate the tarball that will end up on NPM servers
```

Since we don't include anything from `src/`, I moved the TypeScript typings to the package root to avoid having to copy things around.
@eli-darkly eli-darkly requested a review from apucacao August 25, 2018 01:24
@eli-darkly eli-darkly merged commit 85940ba into master Aug 27, 2018
eli-darkly added a commit that referenced this pull request Dec 7, 2018
(4) refactor config validation + make config available to platform client
@eli-darkly eli-darkly deleted the 2.5.0 branch November 5, 2019 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants