…l/examples/complete (#855)

Bumps [next](https://github.com/vercel/next.js) from 14.2.21 to 14.2.26.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/vercel/next.js/releases">next's
releases</a>.</em></p>
<blockquote>
<h2>v14.2.26</h2>
<blockquote>
<p>[!NOTE]<br />
This release is backporting bug fixes. It does <strong>not</strong>
include all pending features/changes on canary.</p>
</blockquote>
<h3>Core Changes</h3>
<ul>
<li>Match subrequest handling for edge and node (<a
href="https://redirect.github.com/vercel/next.js/issues/77476">#77476</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/vercel/next.js/commit/10a042cdca294fd1c6852b320954bc6ccc6064e7"><code>10a042c</code></a>
v14.2.26</li>
<li><a
href="https://github.com/vercel/next.js/commit/8a511d6a22d38132c79b8f70ee29713d42225802"><code>8a511d6</code></a>
Match subrequest handling for edge and node (<a
href="https://redirect.github.com/vercel/next.js/issues/77476">#77476</a>)</li>
<li><a
href="https://github.com/vercel/next.js/commit/d36a1f3c3547b0cb807f30c14aa6250a932349c8"><code>d36a1f3</code></a>
v14.2.25</li>
<li><a
href="https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48"><code>5fd3ae8</code></a>
[backport] Update middleware request header (<a
href="https://redirect.github.com/vercel/next.js/issues/77202">#77202</a>)</li>
<li><a
href="https://github.com/vercel/next.js/commit/756be15c4cfecb6fae1c69cae7cfaf336423b6cf"><code>756be15</code></a>
v14.2.24</li>
<li><a
href="https://github.com/vercel/next.js/commit/ba6453d5efbb1dcb282c39d372b48d60de59fa2c"><code>ba6453d</code></a>
fix corepack keys</li>
<li><a
href="https://github.com/vercel/next.js/commit/c482c2072f6eb3f7bd656bc05e100ed54dce3636"><code>c482c20</code></a>
[backport v14] fix: ensure lint worker errors aren't silenced (<a
href="https://redirect.github.com/vercel/next.js/issues/75766">#75766</a>)
(<a
href="https://redirect.github.com/vercel/next.js/issues/75779">#75779</a>)</li>
<li><a
href="https://github.com/vercel/next.js/commit/5791cb677808df1cea625057d6aff95fbf5cd3a0"><code>5791cb6</code></a>
[Backport v14] add additional x-middleware-set-cookie filtering (<a
href="https://redirect.github.com/vercel/next.js/issues/75561">#75561</a>)
(<a
href="https://redirect.github.com/vercel/next.js/issues/75">#75</a>...</li>
<li><a
href="https://github.com/vercel/next.js/commit/8129a6188096c23c68d4151256acbe6d86d2eed3"><code>8129a61</code></a>
test: fix eslint plugin test (<a
href="https://redirect.github.com/vercel/next.js/issues/75687">#75687</a>)</li>
<li><a
href="https://github.com/vercel/next.js/commit/f27ce02b6785a1c7c8f88daf1d2112b5a2e1f34a"><code>f27ce02</code></a>
v14.2.23</li>
<li>Additional commits viewable in <a
href="https://github.com/vercel/next.js/compare/v14.2.21...v14.2.26">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=next&package-manager=npm_and_yarn&previous-version=14.2.21&new-version=14.2.26)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@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)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/launchdarkly/js-core/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: Todd Anderson <tanderson@Todds-MacBook-Pro.local>

#869)

**Requirements**

- [ ] I have added test coverage for new or changed functionality
- [ ] 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**

#868

**Describe the solution you've provided**

Provides Requestor configuration in correct order.

**Describe alternatives you've considered**

None.

**Additional context**

Fixes #868

Edit: in functions with many arguments, consider arguments with an
object, so that it's more clear what values are assigned to which keys.

---------

Co-authored-by: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>

🤖 I have created a release *beep* *boop*
---


<details><summary>jest: 0.1.7</summary>

##
[0.1.7](jest-v0.1.6...jest-v0.1.7)
(2025-05-22)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
* @launchdarkly/react-native-client-sdk bumped from ~10.10.1 to ~10.10.2
</details>

<details><summary>react-native-client-sdk: 10.10.2</summary>

##
[10.10.2](react-native-client-sdk-v10.10.1...react-native-client-sdk-v10.10.2)
(2025-05-22)


### Bug Fixes

* Requestor initialized with wrong withReasons and useReport config
([#869](#869))
([2e095c5](2e095c5))
</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 an initial set of cursor rules. These rules can be changes if
issues are encountered. The goal is to make cursor more adept at working
in this repository.

This PR + #842 should help
to prevent issues like #840.

🤖 I have created a release *beep* *boop*
---


<details><summary>browser-telemetry: 1.0.9</summary>

##
[1.0.9](browser-telemetry-v1.0.8...browser-telemetry-v1.0.9)
(2025-06-03)


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/js-client-sdk bumped from 0.7.0 to 0.7.1
</details>

<details><summary>jest: 0.1.8</summary>

##
[0.1.8](jest-v0.1.7...jest-v0.1.8)
(2025-06-03)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
* @launchdarkly/react-native-client-sdk bumped from ~10.10.2 to ~10.10.3
</details>

<details><summary>js-client-sdk: 0.7.1</summary>

##
[0.7.1](js-client-sdk-v0.7.0...js-client-sdk-v0.7.1)
(2025-06-03)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-client-sdk-common bumped from 1.14.0 to 1.14.1
</details>

<details><summary>js-client-sdk-common: 1.14.1</summary>

##
[1.14.1](js-client-sdk-common-v1.14.0...js-client-sdk-common-v1.14.1)
(2025-06-03)


### Bug Fixes

* Discard events from closed connections.
([#867](#867))
([8119afe](8119afe))
</details>

<details><summary>react-native-client-sdk: 10.10.3</summary>

##
[10.10.3](react-native-client-sdk-v10.10.2...react-native-client-sdk-v10.10.3)
(2025-06-03)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-client-sdk-common bumped from 1.14.0 to 1.14.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>

Scaffolds the combined browser package. This is a package with
pre-configured observability.

**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

This PR adds new changes to LdClientImpl to utilize FDv2 as an
experimental feature.
This PR also moves changes for FDv2 from the temporary holding branch to
main.

---------

Co-authored-by: Todd Anderson <tanderson@Todds-MacBook-Pro.local>

Co-authored-by: Todd Anderson <tanderson@Todds-MacBook-Pro.local>

Co-authored-by: Todd Anderson <127344469+tanderson-ld@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**

@abarker-launchdarkly added initMetadata support while I was working on
FDv2 data sources. This catches the FDv2 datasources up to FDv1
implementations on main.

**Describe the solution you've provided**

Similar to existing FDv1 approach.

---------

Co-authored-by: Todd Anderson <tanderson@Todds-MacBook-Pro.local>

This adds plugin support for the node server SDK.

Plugin support is leaf-SDK specific because plugins use the interface of
the SDK. The interface of the SDK has slightly different capabilities
based on implementation.

Unfortunately this isn't a simple problem to tackle with regards to
organization. We could use composition with the common functionality
being generic over the SDK interface. Doing so would require some
breaking changes to all the SDK implementation, but could be worth it in
the future.

For not though we have to settle for some complexity with the plugin
interface being defined per-sdk and the call to the initialization code
being per-sdk.

This was able to re-use the generic types and functions which means this
isn't very much code.

This SDK had another complexity which is the event emitter. For
convenient implementation of events we were using a mixin, but this
mixin approach means we didn't have the full interface of the SDK
available at the construction time of the SDK. So this PR moves the
emitter implementation into the node client.

### Description
- DynamoDB have rate limit, when we hit read cap, AWS SDK Client will
throw an exception, but in the implementation it was using callback. So
the callback function will never be called.
- So the value will never return to end of client.
- An uncaught exception may crash backend application in some cases



**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)
- [x] I have validated my changes against all supported platform
versions
- the fix is aiming for node server sdk with dynamodb, should be
compatible

**Related issues**

N/A

**Describe the solution you've provided**

- try catch the error and pass undefined to callback function

**Describe alternatives you've considered**
- 1. don't use callback, this is a common and typical issue with mixing
callback, promise and async/await
- 2. to have a error type for callback. usually callback have two
parameters:
```ts
callback: (value, error) -> void
```

**Additional note**
- to cover this kind issue, better to have a integration test, we are
using Nock to re-produce this issue in our internal, but LD isn't using
such a tool, so we didn't at test in PR.

---------

Co-authored-by: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>

🤖 I have created a release *beep* *boop*
---


<details><summary>akamai-edgeworker-sdk-common: 2.0.8</summary>

##
[2.0.8](akamai-edgeworker-sdk-common-v2.0.7...akamai-edgeworker-sdk-common-v2.0.8)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common bumped from ^2.15.2 to ^2.16.0
</details>

<details><summary>akamai-server-base-sdk: 3.0.8</summary>

##
[3.0.8](akamai-server-base-sdk-v3.0.7...akamai-server-base-sdk-v3.0.8)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
* @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.7 to
^2.0.8
    * @launchdarkly/js-server-sdk-common bumped from ^2.15.2 to ^2.16.0
</details>

<details><summary>akamai-server-edgekv-sdk: 1.4.10</summary>

##
[1.4.10](akamai-server-edgekv-sdk-v1.4.9...akamai-server-edgekv-sdk-v1.4.10)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
* @launchdarkly/akamai-edgeworker-sdk-common bumped from ^2.0.7 to
^2.0.8
    * @launchdarkly/js-server-sdk-common bumped from ^2.15.2 to ^2.16.0
</details>

<details><summary>browser-telemetry: 1.0.10</summary>

##
[1.0.10](browser-telemetry-v1.0.9...browser-telemetry-v1.0.10)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/js-client-sdk bumped from 0.7.1 to 0.8.0
</details>

<details><summary>cloudflare-server-sdk: 2.7.8</summary>

##
[2.7.8](cloudflare-server-sdk-v2.7.7...cloudflare-server-sdk-v2.7.8)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.6 to 2.6.7
</details>

<details><summary>fastly-server-sdk: 0.1.8</summary>

##
[0.1.8](fastly-server-sdk-v0.1.7...fastly-server-sdk-v0.1.8)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common bumped from 2.15.2 to 2.16.0
</details>

<details><summary>jest: 0.1.9</summary>

##
[0.1.9](jest-v0.1.8...jest-v0.1.9)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
* @launchdarkly/react-native-client-sdk bumped from ~10.10.3 to ~10.10.4
</details>

<details><summary>js-client-sdk: 0.8.0</summary>

##
[0.8.0](js-client-sdk-v0.7.1...js-client-sdk-v0.8.0)
(2025-06-17)


### Features

* Add support for an identify queue.
([#842](#842))
([78e9a5e](78e9a5e))


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-client-sdk-common bumped from 1.14.1 to 1.15.0
</details>

<details><summary>js-client-sdk-common: 1.15.0</summary>

##
[1.15.0](js-client-sdk-common-v1.14.1...js-client-sdk-common-v1.15.0)
(2025-06-17)


### Features

* Add support for an identify queue.
([#842](#842))
([78e9a5e](78e9a5e))
</details>

<details><summary>js-server-sdk-common: 2.16.0</summary>

##
[2.16.0](js-server-sdk-common-v2.15.2...js-server-sdk-common-v2.16.0)
(2025-06-17)


### Features

* Add plugin support for node.
([#880](#880))
([6b7bf7e](6b7bf7e))
</details>

<details><summary>js-server-sdk-common-edge: 2.6.7</summary>

##
[2.6.7](js-server-sdk-common-edge-v2.6.6...js-server-sdk-common-edge-v2.6.7)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common bumped from 2.15.2 to 2.16.0
</details>

<details><summary>node-server-sdk: 9.10.0</summary>

##
[9.10.0](node-server-sdk-v9.9.2...node-server-sdk-v9.10.0)
(2025-06-17)


### Features

* Add plugin support for node.
([#880](#880))
([6b7bf7e](6b7bf7e))


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common bumped from 2.15.2 to 2.16.0
</details>

<details><summary>node-server-sdk-dynamodb: 6.2.12</summary>

##
[6.2.12](node-server-sdk-dynamodb-v6.2.11...node-server-sdk-dynamodb-v6.2.12)
(2025-06-17)


### Bug Fixes

* uncaught DynamoDB exception
([#888](#888))
([91ff683](91ff683))


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/node-server-sdk bumped from 9.9.2 to 9.10.0
  * peerDependencies
    * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.0
</details>

<details><summary>node-server-sdk-otel: 1.3.0</summary>

##
[1.3.0](node-server-sdk-otel-v1.2.2...node-server-sdk-otel-v1.3.0)
(2025-06-17)


### Features

* Update OTEL tracing hook with latest conventions.
([#887](#887))
([245f1a3](245f1a3))


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/node-server-sdk bumped from 9.9.2 to 9.10.0
  * peerDependencies
    * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.0
</details>

<details><summary>node-server-sdk-redis: 4.2.12</summary>

##
[4.2.12](node-server-sdk-redis-v4.2.11...node-server-sdk-redis-v4.2.12)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/node-server-sdk bumped from 9.9.2 to 9.10.0
  * peerDependencies
    * @launchdarkly/node-server-sdk bumped from >=9.4.3 to >=9.10.0
</details>

<details><summary>react-native-client-sdk: 10.10.4</summary>

##
[10.10.4](react-native-client-sdk-v10.10.3...react-native-client-sdk-v10.10.4)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-client-sdk-common bumped from 1.14.1 to 1.15.0
</details>

<details><summary>server-sdk-ai: 0.9.9</summary>

##
[0.9.9](server-sdk-ai-v0.9.8...server-sdk-ai-v0.9.9)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * devDependencies
    * @launchdarkly/js-server-sdk-common bumped from 2.15.2 to 2.16.0
  * peerDependencies
    * @launchdarkly/js-server-sdk-common bumped from 2.x to 2.16.0
</details>

<details><summary>vercel-server-sdk: 1.3.31</summary>

##
[1.3.31](vercel-server-sdk-v1.3.30...vercel-server-sdk-v1.3.31)
(2025-06-17)


### Dependencies

* The following workspace dependencies were updated
  * dependencies
    * @launchdarkly/js-server-sdk-common-edge bumped from 2.6.6 to 2.6.7
</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>