chore: merging main into FDv2 holding branch #829
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After the client is registered there isn't any further use for the pending events.
This PR vendors tracekit to alleviate some issues with ESM compatibility. Currently the typescript conversion is minimal. It adds the types which are largely compatible and leaves most of it reasonably unchanged. This PR does not port the tests from tracekit to this repository. A subsequent PR will do this. BEGIN_COMMIT_OVERRIDE feat: Vendor TraceKit feat: Export browser-telemetry initialization method. END_COMMIT_OVERRIDE Jira: EMSR-14 Jira: EMSR-15
This build does not yet work on ubuntu 24.04.
Port TraceKit tests for remaining TraceKit functionality. This is a minimal port to typescript.
This PR adds the ability to specify a filter that runs when adding any breadcrumb. The filter can return a modified breadcrumb, or return undefined to filter the breadcrumb entirely. This could be used to redact any information which a customer doesn't want in a bread crumb. --------- Co-authored-by: Stacy Harrison <[email protected]>
Adds the ability to specify a logger and to also use the base SDK logger when possible. The base SDK of a 3.x version does not expose the logger, but 4.x will. There is a minimal replication of the warning level of the logging interface to allow compatibility with both the 3.x SDK and the 4.x SDK. Prefixing is done at message time instead of as part of the logger. Potentially it could be ideal to do it in the logger, but this approach makes it clear that the interpolation supported by most browser loggers will not come into play. (Where if the logger does this prefixing it is either complex or you lose the sprintf style formatting support.) Some earlier log messages has been added, but a logger instance was not yet available.
This PR adds an event which is emitted when a session is started. It also removes some unused code related to session replay. BEGIN_COMMIT_OVERRIDE feat: Add support for the session init event. chore: Remove session capture until session replay is added. END_COMMIT_OVERRIDE
This PR adds a singleton interface to the EM SDK to simplify common usage. You can still create individual browser telemetry instances, but there is a default instance with module level functions for each operation. Minimal example. ``` import * as LDTelemetry from '@launchdarkly/browser-telemetry` LDTelemetry.initTelemetry(); LDTelemetry.register(ldClient); // For manual error capture. LDTelemetry.captureError(someError); ``` --------- Co-authored-by: Stacy Harrison <[email protected]>
This is a compatibility improvement PR intended to make the telemetry package less dependent on a specific SDK package. The inspector interface between 3.x and 4.x has some minor differences and this provides a more broad interface that is compatible with both.
There was a mistake in checking the filters option for breadcrumbs. This fixes the issue and ensures the all options parsing doesn't have any warnings logged.
This PR adds support for error level filtering. This is the highest level filter type capable of filtering on any data. Other filters are provided to simplify the implementation of filtering across all error types. Breadcrumb filters could be implemented in terms of an error filter, but they would have higher complexity and different performance characteristics. For example with a breadcrumb filter we filter that breadcrumb regardless of how many events it may appear in, versus having to filter that same breadcrumb each time an event is captures. Custom url filters operate at the HTTP capture level similarly reducing the frequency of redaction.
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 1.3.3</summary> ## [1.3.3](akamai-edgeworker-sdk-common-v1.3.2...akamai-edgeworker-sdk-common-v1.3.3) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.10.0 to ^2.11.0 </details> <details><summary>akamai-server-base-sdk: 2.1.21</summary> ## [2.1.21](akamai-server-base-sdk-v2.1.20...akamai-server-base-sdk-v2.1.21) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^1.3.2 to ^1.3.3 * @launchdarkly/js-server-sdk-common bumped from ^2.10.0 to ^2.11.0 </details> <details><summary>akamai-server-edgekv-sdk: 1.3.1</summary> ## [1.3.1](akamai-server-edgekv-sdk-v1.3.0...akamai-server-edgekv-sdk-v1.3.1) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^1.3.2 to ^1.3.3 * @launchdarkly/js-server-sdk-common bumped from ^2.10.0 to ^2.11.0 </details> <details><summary>cloudflare-server-sdk: 2.6.4</summary> ## [2.6.4](cloudflare-server-sdk-v2.6.3...cloudflare-server-sdk-v2.6.4) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.5.2 to 2.5.3 </details> <details><summary>js-client-sdk: 0.4.0</summary> ## [0.4.0](js-client-sdk-v0.3.3...js-client-sdk-v0.4.0) (2025-01-22) ### Features * Enable source maps with inlined sources for browser SDK. ([#734](#734)) ([c2a87b1](c2a87b1)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.1 to 1.12.2 </details> <details><summary>js-client-sdk-common: 1.12.2</summary> ## [1.12.2](js-client-sdk-common-v1.12.1...js-client-sdk-common-v1.12.2) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.12.0 to 2.13.0 </details> <details><summary>js-sdk-common: 2.13.0</summary> ## [2.13.0](js-sdk-common-v2.12.0...js-sdk-common-v2.13.0) (2025-01-22) ### Features * Adds StreamingProcessor for FDv2 to sdk-server package. ([#707](#707)) ([7f5c275](7f5c275)) ### Bug Fixes * Remove outdated reference to geolocation. ([#719](#719)) ([0eeb3b6](0eeb3b6)) </details> <details><summary>js-server-sdk-common: 2.11.0</summary> ## [2.11.0](js-server-sdk-common-v2.10.0...js-server-sdk-common-v2.11.0) (2025-01-22) ### Features * Adds StreamingProcessor for FDv2 to sdk-server package. ([#707](#707)) ([7f5c275](7f5c275)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.12.0 to 2.13.0 </details> <details><summary>js-server-sdk-common-edge: 2.5.3</summary> ## [2.5.3](js-server-sdk-common-edge-v2.5.2...js-server-sdk-common-edge-v2.5.3) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.10.0 to 2.11.0 </details> <details><summary>node-server-sdk: 9.7.3</summary> ## [9.7.3](node-server-sdk-v9.7.2...node-server-sdk-v9.7.3) (2025-01-22) ### Bug Fixes * Fix typo in proxy-authorization header for basic authentication. ([#720](#720)) ([220b6d6](220b6d6)), closes [#718](#718) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.10.0 to 2.11.0 </details> <details><summary>node-server-sdk-dynamodb: 6.2.3</summary> ## [6.2.3](node-server-sdk-dynamodb-v6.2.2...node-server-sdk-dynamodb-v6.2.3) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.2 to 9.7.3 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.3 </details> <details><summary>node-server-sdk-otel: 1.1.3</summary> ## [1.1.3](node-server-sdk-otel-v1.1.2...node-server-sdk-otel-v1.1.3) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.2 to 9.7.3 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.3 </details> <details><summary>node-server-sdk-redis: 4.2.3</summary> ## [4.2.3](node-server-sdk-redis-v4.2.2...node-server-sdk-redis-v4.2.3) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.2 to 9.7.3 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.3 </details> <details><summary>react-native-client-sdk: 10.9.4</summary> ## [10.9.4](react-native-client-sdk-v10.9.3...react-native-client-sdk-v10.9.4) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.1 to 1.12.2 </details> <details><summary>server-sdk-ai: 0.7.1</summary> ## [0.7.1](server-sdk-ai-v0.7.0...server-sdk-ai-v0.7.1) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.10.0 to 2.11.0 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.11.0 </details> <details><summary>vercel-server-sdk: 1.3.22</summary> ## [1.3.22](vercel-server-sdk-v1.3.21...vercel-server-sdk-v1.3.22) (2025-01-22) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.5.2 to 2.5.3 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add release-please support for browser-telemetry and address a number of minor issues. BEGIN_COMMIT_OVERRIDE chore: Add browser-telemetry to release please. fix: Export BrowserTelemetry, BrowserTelemetryInspector, and ImplementsCrumb. chore: Update documentation comment links that were invalid. feat: Rename initializeTelemetryInstance to initTelemetryInstance for consistency with initTelemetry. END_COMMIT_OVERRIDE
🤖 I have created a release *beep* *boop* --- <details><summary>browser-telemetry: 0.1.0</summary> ## [0.1.0](browser-telemetry-v0.0.9...browser-telemetry-v0.1.0) (2025-01-22) ### ⚠ BREAKING CHANGES * Updated AI config interface. ([#697](#697)) ### Features * Add basic logging support for browser-telemetry. ([#736](#736)) ([2ef1486](2ef1486)) * Add browser telemetry options. ([#675](#675)) ([c8352b2](c8352b2)) * Add browser-telemetry API types. ([#669](#669)) ([89967ee](89967ee)) * Add DOM collectors. ([#672](#672)) ([4473a06](4473a06)) * Add http collectors. ([#673](#673)) ([6e60ddc](6e60ddc)) * Add singleton support for browser-telemetry. ([#739](#739)) ([68a3b87](68a3b87)) * Add stack trace parsing. ([#676](#676)) ([ca1dd49](ca1dd49)) * Add support for breadcrumb filtering. ([#733](#733)) ([5c327a1](5c327a1)) * Add support for the session init event. ([320c07d](320c07d)) * Add the ability to filter errors. ([#743](#743)) ([5cffb2b](5cffb2b)) * Export browser-telemetry initialization method. ([d1b364e](d1b364e)) * Implement browser telemetry client. ([#691](#691)) ([db74a99](db74a99)) * Make browser-telemetry specific inspector type. ([#741](#741)) ([14ecdb3](14ecdb3)) * Random uuid for telemetry package. ([#689](#689)) ([4cf34f9](4cf34f9)) * Rename initializeTelemetryInstance to initTelemetryInstance for consistency with initTelemetry. ([257734f](257734f)) * Source maps with inline sources for browser-telemetry. ([#735](#735)) ([1656a85](1656a85)) * Updated AI config interface. ([#697](#697)) ([cd72ea8](cd72ea8)) * Vendor TraceKit ([d1b364e](d1b364e)) ### Bug Fixes * Clear pending events buffer when registered. ([#727](#727)) ([b6ad7df](b6ad7df)) * Export BrowserTelemetry, BrowserTelemetryInspector, and ImplementsCrumb. ([257734f](257734f)) * Fix breadcrumb filter option parsing. ([#742](#742)) ([833f4ce](833f4ce)) * Remove BrowserTelemetry until more types are available. ([#671](#671)) ([796b8a3](796b8a3)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
During initialization the js-client-sdk does some context processing. This is an async operation which will add keys to anonymous contexts. Being as this doesn't happen synchronously within the initialization call there is a possibility that you register the telemetry SDK before that initialization is complete. This PR updates the registration to attempt to wait for initialization. This is a larger window than we need to wait, but ensures that process will be complete.
🤖 I have created a release *beep* *boop* --- <details><summary>browser-telemetry: 0.1.1</summary> ## [0.1.1](browser-telemetry-v0.1.0...browser-telemetry-v0.1.1) (2025-01-23) ### Bug Fixes * Fix race condition with client registration. ([#750](#750)) ([d2ac2e2](d2ac2e2)) </details> <details><summary>server-sdk-ai: 0.8.0</summary> ## [0.8.0](server-sdk-ai-v0.7.1...server-sdk-ai-v0.8.0) (2025-01-23) ### Features * track timeToFirstToken in LDAIConfigTracker ([#749](#749)) ([c97674f](c97674f)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- <details><summary>browser-telemetry: 0.2.0</summary> ## [0.2.0](browser-telemetry-v0.1.1...browser-telemetry-v0.2.0) (2025-01-23) ### Features * Add support for filtering username/password URL authority. ([#751](#751)) ([62ab9fb](62ab9fb)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Molly <[email protected]>
🤖 I have created a release *beep* *boop* --- <details><summary>server-sdk-ai: 0.8.1</summary> ## [0.8.1](server-sdk-ai-v0.8.0...server-sdk-ai-v0.8.1) (2025-01-24) ### Bug Fixes * Correct documentation for AI config function. ([#754](#754)) ([0bdb0be](0bdb0be)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- <details><summary>react-native-client-sdk: 10.9.5</summary> ## [10.9.5](react-native-client-sdk-v10.9.4...react-native-client-sdk-v10.9.5) (2025-01-24) ### Bug Fixes * **react-native:** check for nullability in SettingsManager?.settings ([#758](#758)) ([3449934](3449934)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
**Requirements** - [x] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Related issues** Provide links to any issues in this repository or elsewhere relating to this pull request. **Describe the solution you've provided** Provide a clear and concise description of what you expect to happen. **Describe alternatives you've considered** Provide a clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context about the pull request here. --------- Co-authored-by: Ryan Lamb <[email protected]>
🤖 I have created a release *beep* *boop* --- <details><summary>jest: 0.1.0</summary> ## 0.1.0 (2025-01-24) ### Features * Implement jest mocks for react-native. ([#535](#535)) ([aee09c8](aee09c8)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
**Requirements** - [ ] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [ ] I have validated my changes against all supported platform versions **Related issues** https://launchdarkly.atlassian.net/browse/DOCS-973 **Describe the solution you've provided** package.json `description` field for Fastly is incorrect, this PR updates it **Describe alternatives you've considered** n/a **Additional context** I'm not sure what, if anything, needs to happen after this update (is a patch release required for this to get picked up anywhere?)
…EADME (#800) This PR adds badges for Fastly to the table in the main README.md and in the Fastly README. You can see what these pages look like on this branch: - [README.md](https://github.com/launchdarkly/js-core/blob/5981d32eec5c02405d042e800eba5c7ef2e2dcf2/README.md) - [packages/sdk/fastly/README.md](https://github.com/launchdarkly/js-core/blob/5981d32eec5c02405d042e800eba5c7ef2e2dcf2/packages/sdk/fastly/README.md)
Start adding some development guidelines to the contributing doc.
**Requirements** - [ ] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [ ] I have validated my changes against all supported platform versions **Related issues** https://launchdarkly.atlassian.net/browse/DOCS-2117 **Describe the solution you've provided** Style guide change requires an update in capitalization here.
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.1</summary> ## [2.0.1](akamai-edgeworker-sdk-common-v2.0.0...akamai-edgeworker-sdk-common-v2.0.1) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.11.1 to ^2.12.0 </details> <details><summary>akamai-server-base-sdk: 3.0.1</summary> ## [3.0.1](akamai-server-base-sdk-v3.0.0...akamai-server-base-sdk-v3.0.1) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.0 to ^2.0.1 * @launchdarkly/js-server-sdk-common bumped from ^2.11.1 to ^2.12.0 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.3</summary> ## [1.4.3](akamai-server-edgekv-sdk-v1.4.2...akamai-server-edgekv-sdk-v1.4.3) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.0 to ^2.0.1 * @launchdarkly/js-server-sdk-common bumped from ^2.11.1 to ^2.12.0 </details> <details><summary>cloudflare-server-sdk: 2.7.0</summary> ## [2.7.0](cloudflare-server-sdk-v2.6.5...cloudflare-server-sdk-v2.7.0) (2025-03-17) ### Features * Add TTL caching for data store ([#801](#801)) ([c1de485](c1de485)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.5.4 to 2.6.0 </details> <details><summary>fastly-server-sdk: 0.1.1</summary> ## [0.1.1](fastly-server-sdk-v0.1.0...fastly-server-sdk-v0.1.1) (2025-03-17) ### Bug Fixes * Remove logging of SDK option configurations ([#806](#806)) ([a76d196](a76d196)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.11.1 to 2.12.0 </details> <details><summary>js-server-sdk-common: 2.12.0</summary> ## [2.12.0](js-server-sdk-common-v2.11.1...js-server-sdk-common-v2.12.0) (2025-03-17) ### Features * Export internalServer module for internal LD usage ([#804](#804)) ([ec43ac8](ec43ac8)) </details> <details><summary>js-server-sdk-common-edge: 2.6.0</summary> ## [2.6.0](js-server-sdk-common-edge-v2.5.4...js-server-sdk-common-edge-v2.6.0) (2025-03-17) ### Features * Add TTL caching for data store ([#801](#801)) ([c1de485](c1de485)) ### Bug Fixes * Remove logging of SDK option configurations ([#806](#806)) ([a76d196](a76d196)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.11.1 to 2.12.0 </details> <details><summary>node-server-sdk: 9.7.5</summary> ## [9.7.5](node-server-sdk-v9.7.4...node-server-sdk-v9.7.5) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.11.1 to 2.12.0 </details> <details><summary>node-server-sdk-dynamodb: 6.2.5</summary> ## [6.2.5](node-server-sdk-dynamodb-v6.2.4...node-server-sdk-dynamodb-v6.2.5) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.4 to 9.7.5 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.5 </details> <details><summary>node-server-sdk-otel: 1.1.5</summary> ## [1.1.5](node-server-sdk-otel-v1.1.4...node-server-sdk-otel-v1.1.5) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.4 to 9.7.5 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.5 </details> <details><summary>node-server-sdk-redis: 4.2.5</summary> ## [4.2.5](node-server-sdk-redis-v4.2.4...node-server-sdk-redis-v4.2.5) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.4 to 9.7.5 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.5 </details> <details><summary>server-sdk-ai: 0.9.2</summary> ## [0.9.2](server-sdk-ai-v0.9.1...server-sdk-ai-v0.9.2) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.11.1 to 2.12.0 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.12.0 </details> <details><summary>vercel-server-sdk: 1.3.24</summary> ## [1.3.24](vercel-server-sdk-v1.3.23...vercel-server-sdk-v1.3.24) (2025-03-17) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.5.4 to 2.6.0 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ption (#808) **Requirements** - [x] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Related issues** https://launchdarkly.atlassian.net/browse/SDK-1132 **Describe the solution you've provided** Previously the timeout was cancelled in a `then()` and would be skipped if the base promise threw an exception. The cancelation was moved to `finally()` where it will always be called regardless of an exception. **Describe alternatives you've considered** N/A **Additional context** N/A
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.2</summary> ## [2.0.2](akamai-edgeworker-sdk-common-v2.0.1...akamai-edgeworker-sdk-common-v2.0.2) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.12.0 to ^2.12.1 </details> <details><summary>akamai-server-base-sdk: 3.0.2</summary> ## [3.0.2](akamai-server-base-sdk-v3.0.1...akamai-server-base-sdk-v3.0.2) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.1 to ^2.0.2 * @launchdarkly/js-server-sdk-common bumped from ^2.12.0 to ^2.12.1 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.4</summary> ## [1.4.4](akamai-server-edgekv-sdk-v1.4.3...akamai-server-edgekv-sdk-v1.4.4) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.1 to ^2.0.2 * @launchdarkly/js-server-sdk-common bumped from ^2.12.0 to ^2.12.1 </details> <details><summary>cloudflare-server-sdk: 2.7.1</summary> ## [2.7.1](cloudflare-server-sdk-v2.7.0...cloudflare-server-sdk-v2.7.1) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.0 to 2.6.1 </details> <details><summary>fastly-server-sdk: 0.1.2</summary> ## [0.1.2](fastly-server-sdk-v0.1.1...fastly-server-sdk-v0.1.2) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.0 to 2.12.1 </details> <details><summary>js-server-sdk-common: 2.12.1</summary> ## [2.12.1](js-server-sdk-common-v2.12.0...js-server-sdk-common-v2.12.1) (2025-03-21) ### Bug Fixes * Fix cancelling timeout when waitForInitialization throws an exception ([#808](#808)) ([bb3c950](bb3c950)) </details> <details><summary>js-server-sdk-common-edge: 2.6.1</summary> ## [2.6.1](js-server-sdk-common-edge-v2.6.0...js-server-sdk-common-edge-v2.6.1) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.0 to 2.12.1 </details> <details><summary>node-server-sdk: 9.7.6</summary> ## [9.7.6](node-server-sdk-v9.7.5...node-server-sdk-v9.7.6) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.0 to 2.12.1 </details> <details><summary>node-server-sdk-dynamodb: 6.2.6</summary> ## [6.2.6](node-server-sdk-dynamodb-v6.2.5...node-server-sdk-dynamodb-v6.2.6) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.5 to 9.7.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.6 </details> <details><summary>node-server-sdk-otel: 1.1.6</summary> ## [1.1.6](node-server-sdk-otel-v1.1.5...node-server-sdk-otel-v1.1.6) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.5 to 9.7.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.6 </details> <details><summary>node-server-sdk-redis: 4.2.6</summary> ## [4.2.6](node-server-sdk-redis-v4.2.5...node-server-sdk-redis-v4.2.6) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.5 to 9.7.6 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.6 </details> <details><summary>server-sdk-ai: 0.9.3</summary> ## [0.9.3](server-sdk-ai-v0.9.2...server-sdk-ai-v0.9.3) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.0 to 2.12.1 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.12.1 </details> <details><summary>vercel-server-sdk: 1.3.25</summary> ## [1.3.25](vercel-server-sdk-v1.3.24...vercel-server-sdk-v1.3.25) (2025-03-21) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.0 to 2.6.1 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
**Requirements** - [x] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Describe the solution you've provided** - Support inlining context for custom events. The logic for this needs to happen in EventProcessor which is shared between server and client sdks in js-core. It has been verified with product analytics that this is ok for the client sdks. - Support inlining context for migration events. This causes a change in the public interface for `LDClient.trackMigration` where the `LDMigrationOpEvent` parameter has been modified. `contextKeys` has been made optional and deprecated in favor of `context` and all internal uses of `LDMigrationOpEvent` have been changed to use `context`. BEGIN_COMMIT_OVERRIDE feat: Support inline context for custom and migration events fix: Deprecate LDMigrationOpEvent.contextKeys in favor of LDMigrationOpEvent.context END_COMMIT_OVERRIDE
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.3</summary> ## [2.0.3](akamai-edgeworker-sdk-common-v2.0.2...akamai-edgeworker-sdk-common-v2.0.3) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.12.1 to ^2.13.0 </details> <details><summary>akamai-server-base-sdk: 3.0.3</summary> ## [3.0.3](akamai-server-base-sdk-v3.0.2...akamai-server-base-sdk-v3.0.3) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.2 to ^2.0.3 * @launchdarkly/js-server-sdk-common bumped from ^2.12.1 to ^2.13.0 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.5</summary> ## [1.4.5](akamai-server-edgekv-sdk-v1.4.4...akamai-server-edgekv-sdk-v1.4.5) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.2 to ^2.0.3 * @launchdarkly/js-server-sdk-common bumped from ^2.12.1 to ^2.13.0 </details> <details><summary>browser-telemetry: 1.0.3</summary> ## [1.0.3](browser-telemetry-v1.0.2...browser-telemetry-v1.0.3) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-client-sdk bumped from 0.4.1 to 0.5.0 </details> <details><summary>cloudflare-server-sdk: 2.7.2</summary> ## [2.7.2](cloudflare-server-sdk-v2.7.1...cloudflare-server-sdk-v2.7.2) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.1 to 2.6.2 </details> <details><summary>fastly-server-sdk: 0.1.3</summary> ## [0.1.3](fastly-server-sdk-v0.1.2...fastly-server-sdk-v0.1.3) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.1 to 2.13.0 </details> <details><summary>jest: 0.1.2</summary> ## [0.1.2](jest-v0.1.1...jest-v0.1.2) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/react-native-client-sdk bumped from ~10.9.6 to ~10.9.7 </details> <details><summary>js-client-sdk: 0.5.0</summary> ## [0.5.0](js-client-sdk-v0.4.1...js-client-sdk-v0.5.0) (2025-03-26) ### Features * Support inline context for custom and migration events ([6aadf04](6aadf04)) ### Bug Fixes * Deprecate LDMigrationOpEvent.contextKeys in favor of LDMigrationOpEvent.context ([6aadf04](6aadf04)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.3 to 1.12.4 </details> <details><summary>js-client-sdk-common: 1.12.4</summary> ## [1.12.4](js-client-sdk-common-v1.12.3...js-client-sdk-common-v1.12.4) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.13.0 to 2.14.0 </details> <details><summary>js-sdk-common: 2.14.0</summary> ## [2.14.0](js-sdk-common-v2.13.0...js-sdk-common-v2.14.0) (2025-03-26) ### Features * Support inline context for custom and migration events ([6aadf04](6aadf04)) ### Bug Fixes * Deprecate LDMigrationOpEvent.contextKeys in favor of LDMigrationOpEvent.context ([6aadf04](6aadf04)) </details> <details><summary>js-server-sdk-common: 2.13.0</summary> ## [2.13.0](js-server-sdk-common-v2.12.1...js-server-sdk-common-v2.13.0) (2025-03-26) ### Features * Support inline context for custom and migration events ([6aadf04](6aadf04)) ### Bug Fixes * Deprecate LDMigrationOpEvent.contextKeys in favor of LDMigrationOpEvent.context ([6aadf04](6aadf04)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.13.0 to 2.14.0 </details> <details><summary>js-server-sdk-common-edge: 2.6.2</summary> ## [2.6.2](js-server-sdk-common-edge-v2.6.1...js-server-sdk-common-edge-v2.6.2) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.1 to 2.13.0 </details> <details><summary>node-server-sdk: 9.7.7</summary> ## [9.7.7](node-server-sdk-v9.7.6...node-server-sdk-v9.7.7) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.1 to 2.13.0 </details> <details><summary>node-server-sdk-dynamodb: 6.2.7</summary> ## [6.2.7](node-server-sdk-dynamodb-v6.2.6...node-server-sdk-dynamodb-v6.2.7) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.6 to 9.7.7 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.7 </details> <details><summary>node-server-sdk-otel: 1.1.7</summary> ## [1.1.7](node-server-sdk-otel-v1.1.6...node-server-sdk-otel-v1.1.7) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.6 to 9.7.7 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.7 </details> <details><summary>node-server-sdk-redis: 4.2.7</summary> ## [4.2.7](node-server-sdk-redis-v4.2.6...node-server-sdk-redis-v4.2.7) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.6 to 9.7.7 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.7.7 </details> <details><summary>react-native-client-sdk: 10.9.7</summary> ## [10.9.7](react-native-client-sdk-v10.9.6...react-native-client-sdk-v10.9.7) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.3 to 1.12.4 </details> <details><summary>server-sdk-ai: 0.9.4</summary> ## [0.9.4](server-sdk-ai-v0.9.3...server-sdk-ai-v0.9.4) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.12.1 to 2.13.0 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.13.0 </details> <details><summary>vercel-server-sdk: 1.3.26</summary> ## [1.3.26](vercel-server-sdk-v1.3.25...vercel-server-sdk-v1.3.26) (2025-03-26) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.1 to 2.6.2 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add notes on repo organization and dependencies. This PR is best reviewed with the rich diff 
**Requirements** - [x] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Describe the solution you've provided** LDConfig option `enableEventCompression` was added for js-server-sdk-common and NodeRequests was modified to support gzip compression of POST bodies if this option is enabled.
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.4</summary> ## [2.0.4](akamai-edgeworker-sdk-common-v2.0.3...akamai-edgeworker-sdk-common-v2.0.4) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.13.0 to ^2.14.0 </details> <details><summary>akamai-server-base-sdk: 3.0.4</summary> ## [3.0.4](akamai-server-base-sdk-v3.0.3...akamai-server-base-sdk-v3.0.4) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.3 to ^2.0.4 * @launchdarkly/js-server-sdk-common bumped from ^2.13.0 to ^2.14.0 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.6</summary> ## [1.4.6](akamai-server-edgekv-sdk-v1.4.5...akamai-server-edgekv-sdk-v1.4.6) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.3 to ^2.0.4 * @launchdarkly/js-server-sdk-common bumped from ^2.13.0 to ^2.14.0 </details> <details><summary>browser-telemetry: 1.0.4</summary> ## [1.0.4](browser-telemetry-v1.0.3...browser-telemetry-v1.0.4) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-client-sdk bumped from 0.5.0 to 0.5.1 </details> <details><summary>cloudflare-server-sdk: 2.7.3</summary> ## [2.7.3](cloudflare-server-sdk-v2.7.2...cloudflare-server-sdk-v2.7.3) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.2 to 2.6.3 </details> <details><summary>fastly-server-sdk: 0.1.4</summary> ## [0.1.4](fastly-server-sdk-v0.1.3...fastly-server-sdk-v0.1.4) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.13.0 to 2.14.0 </details> <details><summary>jest: 0.1.3</summary> ## [0.1.3](jest-v0.1.2...jest-v0.1.3) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/react-native-client-sdk bumped from ~10.9.7 to ~10.9.8 </details> <details><summary>js-client-sdk: 0.5.1</summary> ## [0.5.1](js-client-sdk-v0.5.0...js-client-sdk-v0.5.1) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.4 to 1.12.5 </details> <details><summary>js-client-sdk-common: 1.12.5</summary> ## [1.12.5](js-client-sdk-common-v1.12.4...js-client-sdk-common-v1.12.5) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.14.0 to 2.15.0 </details> <details><summary>js-sdk-common: 2.15.0</summary> ## [2.15.0](js-sdk-common-v2.14.0...js-sdk-common-v2.15.0) (2025-04-08) ### Features * Option to use gzip to compress event ([#814](#814)) ([4e91431](4e91431)) </details> <details><summary>js-server-sdk-common: 2.14.0</summary> ## [2.14.0](js-server-sdk-common-v2.13.0...js-server-sdk-common-v2.14.0) (2025-04-08) ### Features * Option to use gzip to compress event ([#814](#814)) ([4e91431](4e91431)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.14.0 to 2.15.0 </details> <details><summary>js-server-sdk-common-edge: 2.6.3</summary> ## [2.6.3](js-server-sdk-common-edge-v2.6.2...js-server-sdk-common-edge-v2.6.3) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.13.0 to 2.14.0 </details> <details><summary>node-server-sdk: 9.8.0</summary> ## [9.8.0](node-server-sdk-v9.7.7...node-server-sdk-v9.8.0) (2025-04-08) ### Features * Option to use gzip to compress event ([#814](#814)) ([4e91431](4e91431)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.13.0 to 2.14.0 </details> <details><summary>node-server-sdk-dynamodb: 6.2.8</summary> ## [6.2.8](node-server-sdk-dynamodb-v6.2.7...node-server-sdk-dynamodb-v6.2.8) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.7 to 9.8.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.8.0 </details> <details><summary>node-server-sdk-otel: 1.1.8</summary> ## [1.1.8](node-server-sdk-otel-v1.1.7...node-server-sdk-otel-v1.1.8) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.7 to 9.8.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.8.0 </details> <details><summary>node-server-sdk-redis: 4.2.8</summary> ## [4.2.8](node-server-sdk-redis-v4.2.7...node-server-sdk-redis-v4.2.8) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.7.7 to 9.8.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.8.0 </details> <details><summary>react-native-client-sdk: 10.9.8</summary> ## [10.9.8](react-native-client-sdk-v10.9.7...react-native-client-sdk-v10.9.8) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.4 to 1.12.5 </details> <details><summary>server-sdk-ai: 0.9.5</summary> ## [0.9.5](server-sdk-ai-v0.9.4...server-sdk-ai-v0.9.5) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.13.0 to 2.14.0 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.14.0 </details> <details><summary>vercel-server-sdk: 1.3.27</summary> ## [1.3.27](vercel-server-sdk-v1.3.26...vercel-server-sdk-v1.3.27) (2025-04-08) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.2 to 2.6.3 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add some additional build information to the contributing documentation.
Convert the contract tests to TypeScript. This is just a straight conversion without any structural improvements. Add the contract tests to the workspace. This allows everything to be linked locally by default.
The browser SDK was incorrectly handling its default flush interval configuration. There are two layers to defaults for the browser SDK. The first is defaults which differ from the base configuration defaults, second is defaults for browser specific configuration. The base defaults were being applied to the browser specific configuration, which meant those changes were being lost and instead the base default was being used instead. Fixes: SDK-1199
🤖 I have created a release *beep* *boop* --- <details><summary>browser-telemetry: 1.0.5</summary> ## [1.0.5](browser-telemetry-v1.0.4...browser-telemetry-v1.0.5) (2025-04-15) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-client-sdk bumped from 0.5.1 to 0.5.2 </details> <details><summary>js-client-sdk: 0.5.2</summary> ## [0.5.2](js-client-sdk-v0.5.1...js-client-sdk-v0.5.2) (2025-04-15) ### Bug Fixes * Handle default flush interval for browser SDK. ([#822](#822)) ([2c1cc7a](2c1cc7a)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
**Requirements** - [x] I have added test coverage for new or changed functionality - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Describe the solution you've provided** If present, `environmentId` is now passed to the HookRunner in the evaluation series. For streaming connections: - Response headers are now attached to the `open` event (launchdarkly/js-eventsource#33) - `StreamingProcessor` passes these headers to the stream listeners via `processJson`. The listener for the PUT event extracts the `environmentId` from the headers and passes this as initialization metadata to the underlying feature store. For polling connections: - `PollingProcessor` retrieves the response headers via the underlying `Requestor` and extracts the `environmentId` from the headers and passes this as initialization metadata to the underlying feature store. LDClient will then call `getInitMetaData()` on the underlying feature store (if the feature store supports it) when executing a hook and pass `environmentId` in the execution series data. Currently only `InMemoryFeatureStore` has been modified to support initialization metadata. This functionality can be added to other feature stores by modifying `init()` to accept the optional `initMetadata` parameter and implementing the optional `getInitMetadata()` method.
🤖 I have created a release *beep* *boop* --- <details><summary>akamai-edgeworker-sdk-common: 2.0.5</summary> ## [2.0.5](akamai-edgeworker-sdk-common-v2.0.4...akamai-edgeworker-sdk-common-v2.0.5) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from ^2.14.0 to ^2.15.0 </details> <details><summary>akamai-server-base-sdk: 3.0.5</summary> ## [3.0.5](akamai-server-base-sdk-v3.0.4...akamai-server-base-sdk-v3.0.5) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.4 to ^2.0.5 * @launchdarkly/js-server-sdk-common bumped from ^2.14.0 to ^2.15.0 </details> <details><summary>akamai-server-edgekv-sdk: 1.4.7</summary> ## [1.4.7](akamai-server-edgekv-sdk-v1.4.6...akamai-server-edgekv-sdk-v1.4.7) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.4 to ^2.0.5 * @launchdarkly/js-server-sdk-common bumped from ^2.14.0 to ^2.15.0 </details> <details><summary>browser-telemetry: 1.0.6</summary> ## [1.0.6](browser-telemetry-v1.0.5...browser-telemetry-v1.0.6) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-client-sdk bumped from 0.5.2 to 0.5.3 </details> <details><summary>cloudflare-server-sdk: 2.7.4</summary> ## [2.7.4](cloudflare-server-sdk-v2.7.3...cloudflare-server-sdk-v2.7.4) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.3 to 2.6.4 </details> <details><summary>fastly-server-sdk: 0.1.5</summary> ## [0.1.5](fastly-server-sdk-v0.1.4...fastly-server-sdk-v0.1.5) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.14.0 to 2.15.0 </details> <details><summary>jest: 0.1.4</summary> ## [0.1.4](jest-v0.1.3...jest-v0.1.4) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/react-native-client-sdk bumped from ~10.9.8 to ~10.9.9 </details> <details><summary>js-client-sdk: 0.5.3</summary> ## [0.5.3](js-client-sdk-v0.5.2...js-client-sdk-v0.5.3) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.5 to 1.12.6 </details> <details><summary>js-client-sdk-common: 1.12.6</summary> ## [1.12.6](js-client-sdk-common-v1.12.5...js-client-sdk-common-v1.12.6) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.15.0 to 2.16.0 </details> <details><summary>js-sdk-common: 2.16.0</summary> ## [2.16.0](js-sdk-common-v2.15.0...js-sdk-common-v2.16.0) (2025-04-16) ### Features * Environment ID support for hooks ([#823](#823)) ([63dc9f9](63dc9f9)) </details> <details><summary>js-server-sdk-common: 2.15.0</summary> ## [2.15.0](js-server-sdk-common-v2.14.0...js-server-sdk-common-v2.15.0) (2025-04-16) ### Features * Environment ID support for hooks ([#823](#823)) ([63dc9f9](63dc9f9)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-sdk-common bumped from 2.15.0 to 2.16.0 </details> <details><summary>js-server-sdk-common-edge: 2.6.4</summary> ## [2.6.4](js-server-sdk-common-edge-v2.6.3...js-server-sdk-common-edge-v2.6.4) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.14.0 to 2.15.0 </details> <details><summary>node-server-sdk: 9.9.0</summary> ## [9.9.0](node-server-sdk-v9.8.0...node-server-sdk-v9.9.0) (2025-04-16) ### Features * Environment ID support for hooks ([#823](#823)) ([63dc9f9](63dc9f9)) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common bumped from 2.14.0 to 2.15.0 </details> <details><summary>node-server-sdk-dynamodb: 6.2.9</summary> ## [6.2.9](node-server-sdk-dynamodb-v6.2.8...node-server-sdk-dynamodb-v6.2.9) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.8.0 to 9.9.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.9.0 </details> <details><summary>node-server-sdk-otel: 1.2.0</summary> ## [1.2.0](node-server-sdk-otel-v1.1.8...node-server-sdk-otel-v1.2.0) (2025-04-16) ### Features * Environment ID support for hooks ([#823](#823)) ([63dc9f9](63dc9f9)) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.8.0 to 9.9.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.9.0 </details> <details><summary>node-server-sdk-redis: 4.2.9</summary> ## [4.2.9](node-server-sdk-redis-v4.2.8...node-server-sdk-redis-v4.2.9) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/node-server-sdk bumped from 9.8.0 to 9.9.0 * peerDependencies * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.9.0 </details> <details><summary>react-native-client-sdk: 10.9.9</summary> ## [10.9.9](react-native-client-sdk-v10.9.8...react-native-client-sdk-v10.9.9) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-client-sdk-common bumped from 1.12.5 to 1.12.6 </details> <details><summary>server-sdk-ai: 0.9.6</summary> ## [0.9.6](server-sdk-ai-v0.9.5...server-sdk-ai-v0.9.6) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * devDependencies * @launchdarkly/js-server-sdk-common bumped from 2.14.0 to 2.15.0 * peerDependencies * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.15.0 </details> <details><summary>vercel-server-sdk: 1.3.28</summary> ## [1.3.28](vercel-server-sdk-v1.3.27...vercel-server-sdk-v1.3.28) (2025-04-16) ### Dependencies * The following workspace dependencies were updated * dependencies * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.3 to 2.6.4 </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Adds support for the track series to the client-side hook implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.