Generated TypeDoc documentation for all types, properties, and methods is now available online at https://launchdarkly.github.io/node-server-sdk/. Currently this will only be for the latest released version.
It is now possible to specify any of the TLS configuration parameters supported by Node's https.request() in the client configuration, so that they will apply to all HTTPS requests made by the SDK. In your client options, add a property called tlsParams whose value is an object containing those parameters, e.g. tlsParams: { ca: 'my trusted CA certificate data' }.
Fixed:
Running the SDK unit tests is now simpler in that the Redis integration can be skipped. See CONTRIBUTING.md.
Note on future releases
The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now node-server-sdk rather than node-client. (Note that node-client-sdk also exists, which is the client-side Node SDK.)
The package name will also change. In the 5.8.0 release, it is still ldclient-node; in all future releases, it will be launchdarkly-node-server-sdk. No further updates to the ldclient-node package will be published after this release.
[5.8.0] - 2019-04-06
Added:
https.request()in the client configuration, so that they will apply to all HTTPS requests made by the SDK. In your client options, add a property calledtlsParamswhose value is an object containing those parameters, e.g.tlsParams: { ca: 'my trusted CA certificate data' }.Fixed:
CONTRIBUTING.md.Note on future releases
The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now
node-server-sdkrather thannode-client. (Note thatnode-client-sdkalso exists, which is the client-side Node SDK.)The package name will also change. In the 5.8.0 release, it is still
ldclient-node; in all future releases, it will belaunchdarkly-node-server-sdk. No further updates to theldclient-nodepackage will be published after this release.