Skip to content
This repository was archived by the owner on May 30, 2024. It is now read-only.

Conversation

@eli-darkly
Copy link
Contributor

[6.0.0-rc.1] - 2021-06-15

This is a release candidate version corresponding to the current projected state of the 6.0.0 release. The final 6.0.0 release may include additional functionality or fixes.

The 6.0.0 major version release is for Node.js compatibility updates and simplifying the SDK's dependencies. Dropping support for obsolete Node.js versions makes it easier to maintain the SDK and keep its dependencies up to date. Simplifying dependencies reduces the size of the SDK bundle, and reduces potential compatibility problems in environments like AWS Lambda.

Added:

  • Added ld.basicLogger, allowing customization of the SDK's simple logging behavior without having to provide a full LDLogger implementation.

Changed:

  • The minimum Node.js version is now 12.0.
  • Updated many dependencies to newer versions and/or more actively maintained packages.

Removed:

  • All types and methods that were deprecated in previous releases have been removed.
  • Removed the bundled Redis integration. This is now provided as a separate package, like the other database integrations; see node-server-sdk-redis. The main SDK package no longer has a dependency on the redis package.
  • Removed the dependency on Winston. An application can still tell the SDK to use a Winston logger instance that the application has created, just as before, but the SDK no longer uses Winston to create a default logger if the application does not specify a logger. Instead, it uses the ld.basicLogger implementation, which has the same behavior as the previous default Winston configuration. Note: If you are using the launchdarkly-node-server-sdk-dynamodb or launchdarkly-node-server-consul database integration packages, you should update them to the latest versions which have also had the Winston dependency removed.
  • Removed the dependency on yaml. This package was only used for the optional file data source functionality. You can still use YAML data files with the file data source if you explicitly install the yaml package in your project; the SDK will automatically detect its presence.

eli-darkly and others added 30 commits May 13, 2019 17:09
update package name + fix some test stuff
…ulnerability with 'extend' (#140)

* bump request to resolve a security vulnerability with extend

* remove incorrect build step

* update language
# Conflicts:
#	package-lock.json
#	package.json
update doc comment for track() with metricValue
Migrate to ES2015 syntax and add linting
@eli-darkly eli-darkly requested a review from bwoskow-ld June 15, 2021 21:37
@eli-darkly eli-darkly merged commit 782d3c5 into master Jun 15, 2021
@eli-darkly eli-darkly deleted the release-6.0.0-rc.1 branch June 15, 2021 23:16
eli-darkly pushed a commit that referenced this pull request Feb 19, 2022
…-source

Implemented DataSource and added Typescript interface documentation
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants