Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

launchdarkly-js-sdk-common

Package Overview
Dependencies
Maintainers
1
Versions
79
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

launchdarkly-js-sdk-common - npm Package Versions

1
8

4.3.0

Diff

Changelog

Source

[4.3.0] - 2022-10-17

Added:

  • Added support for Inspectors that can be used for collecting information for monitoring, analytics, and debugging.
launchdarkly
published 3.8.0 •

launchdarkly
published 4.2.0 •

Changelog

Source

[4.2.0] - 2022-10-03

Removed:

  • Removed seenRequests cache. This cache was used to de-duplicate events, but it has been supplanted with summary events.

Deprecated:

  • The allowFrequentDuplicateEvents configuration has been deprecated because it controlled the behavior of the seenRequests cache.
launchdarkly
published 3.7.0 •

launchdarkly
published 4.1.1 •

Changelog

Source

[4.1.1] - 2022-06-07

Changed:

  • Enforce a 64 character limit for application.id and application.version configuration options.

Fixed:

  • Do not include deleted flags in allFlags.
launchdarkly
published 4.1.0 •

Changelog

Source

[4.1.0] - 2022-04-21

Added:

  • LDOptionsBase.application, for configuration of application metadata that may be used in LaunchDarkly analytics or other product features. This does not affect feature flag evaluations.

Fixed:

  • The baseUrl, streamUrl, and eventsUrl properties now work properly regardless of whether the URL string has a trailing slash. Previously, a trailing slash would cause request URL paths to have double slashes.
launchdarkly
published 3.6.0 •

launchdarkly
published 3.5.1 •

Changelog

Source

[3.5.1] - 2022-02-17

Fixed:

  • If the SDK receives invalid JSON data from a streaming connection (possibly as a result of the connection being cut off), it now uses its regular error-handling logic: the error is emitted as an error event or, if there are no error event listeners, it is logged. Previously, it would be thrown as an unhandled exception.
launchdarkly
published 4.0.3 •

Changelog

Source

[4.0.3] - 2022-02-16

Fixed:

  • If the SDK receives invalid JSON data from a streaming connection (possibly as a result of the connection being cut off), it now uses its regular error-handling logic: the error is emitted as an error event or, if there are no error event listeners, it is logged. Previously, it would be thrown as an unhandled exception.
launchdarkly
published 4.0.2 •

Changelog

Source

[4.0.2] - 2022-01-25

Removed:

  • Removed the version export which was originally a constant inserted by the Rollup build, but was no longer usable since Rollup is no longer being used. The SDKs never used this export, since they have version properties of their own; the version string of launchdarkly-js-sdk-common was never meant to be exposed to applications.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc