feat!: release @launchdarkly/node-client-sdk@4.0.0 - #1834
Conversation
This release ports launchdarkly-node-client-sdk onto js-core. The package moves to @launchdarkly/node-client-sdk and rebases on @launchdarkly/js-client-sdk-common, picking up the shared client-side foundation used by the browser and combined-browser SDKs. Consumers should follow the migration guide for the new initialization flow, extension surfaces (hooks, inspectors, plugins), and the on-disk cache format change. See https://launchdarkly.com/docs/sdk/client-side/node-js for full SDK documentation. BREAKING-CHANGE: The package name changed from `launchdarkly-node-client-sdk` to `@launchdarkly/node-client-sdk`. BREAKING-CHANGE: Initialization is now done with `createClient` and `start` (see docs). BREAKING-CHANGE: Minimum Node version is now `>=18`. BREAKING-CHANGE: The on-disk persistent cache format changed; v3 cache data will not be read by v4 and the anonymous key will be regenerated on first identify. feat!: `identify()` resolves an identify result and no longer throws feat: Evaluation, identify, and track hooks feat: Inspector support for flag and context state feat: Plugin extension surface with `applicationInfo` metadata feat: Runtime connection-mode control via `setConnectionMode` feat: Storage configuration with file-backed default and custom-implementation override feat: TLS configuration via `tlsParams` feat: support client side secure mode with client side id feat: support wrapper header feat: Add useMobileKey option to NodeOptions
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/browser size report |
|
@launchdarkly/js-client-sdk-common size report |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 467b7ba. Configure here.
This release ports launchdarkly-node-client-sdk onto js-core. The package
moves to @launchdarkly/node-client-sdk and rebases on
@launchdarkly/js-client-sdk-common, picking up the shared client-side
foundation used by the browser and combined-browser SDKs. Consumers
should follow the migration guide for the new initialization flow,
extension surfaces (hooks, inspectors, plugins), and the on-disk cache
format change. See https://launchdarkly.com/docs/sdk/client-side/node-js
for full SDK documentation.
BREAKING-CHANGE: The package name changed from
launchdarkly-node-client-sdkto@launchdarkly/node-client-sdk.BREAKING-CHANGE: Initialization is now done with
createClientandstart(see docs).BREAKING-CHANGE: Minimum Node version is now
>=18.BREAKING-CHANGE: The on-disk persistent cache format changed; v3 cache data will not be read by v4 and the anonymous key will be regenerated on first identify.
feat!:
identify()resolves an identify result and no longer throwsfeat: Evaluation, identify, and track hooks
feat: Inspector support for flag and context state
feat: Plugin extension surface with
applicationInfometadatafeat: Runtime connection-mode control via
setConnectionModefeat: Storage configuration with file-backed default and custom-implementation override
feat: TLS configuration via
tlsParamsfeat: support client side secure mode with client side id
feat: support wrapper header
feat: Add useMobileKey option to NodeOptions
Note
Low Risk
Documentation and release tooling only; no runtime SDK code changes in this diff.
Overview
Prepares
@launchdarkly/node-client-sdkfor a 4.0.0 GA release by updating release automation and package docs.release-please-config.jsonstops treatingpackages/sdk/node-clientas a prerelease (bump-minor-pre-major/prerelease) and pins the next release withrelease-as:4.0.0.The node-client README drops the pre-release CAUTION block that warned about API instability and pinning to minor versions.
Reviewed by Cursor Bugbot for commit 467b7ba. Bugbot is set up for automated code reviews on this repo. Configure here.