fix: update launchdarkly-js-sdk-common to 5.8.2

[joker23]

Requirements

• I have added test coverage for new or changed functionality — n/a, dependency bump only
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

Related issues

Picks up the bugfix released in launchdarkly-js-sdk-common v5.8.2 (https://github.com/launchdarkly/js-sdk-common).

Describe the solution you've provided

Bump the launchdarkly-js-sdk-common dependency from 5.8.1 to 5.8.2.

-    "launchdarkly-js-sdk-common": "5.8.1"
+    "launchdarkly-js-sdk-common": "5.8.2"

Uses fix: (matching #341) so release-please cuts a patch release that propagates the fix to downstream consumers.

Also pins @types/node to ^20.0.0. @types/node was previously unpinned (pulled transitively) and had floated to v26, which references lib types (IteratorObject, BuiltinIteratorReturn) that don't exist in typescript ~5.4.5, breaking npm run check-typescript. This failure already exists on main (verified on a clean checkout) and is unrelated to the common bump; the pin is the minimal fix to get check-typescript / CI green again.

Verified locally: npm install, npm test (166 passed), npm run lint:all, and npm run check-typescript all pass.

Describe alternatives you've considered

For the type errors, skipLibCheck in tsconfig would also silence them, but pinning @types/node to a version compatible with the pinned TypeScript is more targeted.

Additional context

Part of rolling out launchdarkly-js-sdk-common v5.8.2 across the client-side JS SDKs (companion PR in node-client-sdk). Downstream packages that depend on this SDK (react-client-sdk, vue-client-sdk, @launchdarkly/toolbar) will pick up the change transitively once this SDK is released.

Link to Devin session: https://app.devin.ai/sessions/3ed6e570c11b4abb80724e0f2bc5f03e
Requested by: @joker23

---

Note

Low Risk
Dependency-only changes with no application logic edits; risk is limited to transitive behavior from the common SDK patch and dev-time typing.

Overview
Pulls in the 5.8.2 patch from launchdarkly-js-sdk-common (replacing 5.8.1) so this browser SDK ships the upstream bugfix on the next patch release.

Adds an explicit devDependency @types/node: ^20.0.0 so check-typescript no longer fails when an unpinned transitive @types/node (e.g. v26) references lib types that TypeScript ~5.4.5 does not provide.

^{Reviewed by Cursor Bugbot for commit ca4b27a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

@cursor review

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[joker23]

Needed to add this type dep to stop types/node from drifting to a higher major version level. Expected since this is an older sdk.

[devin-ai-integration]

Exactly — pinned to ^20.0.0 to keep it within a major compatible with typescript ~5.4.5. Unpinned it had drifted to v26, which references lib types (IteratorObject, BuiltinIteratorReturn) not present in 5.4, breaking check-typescript (reproduces on a clean main).