Closed klujanrosas closed 4 years ago
Hi. Sorry about this! Something went wrong with our last release, and we'll have a new version out ASAP. In the meantime we are unpublishing the 2.16.0 release from npm (which we will only do for a version that's completely broken and unusable, as this is).
Released 2.16.1 which should fix this.
Apologies again - there was an undetected problem with 2.16.1 (not actually a bug, but a feature that had been enabled before the LD web service was ready to handle it) so it has been superseded by 2.16.2.
@eli-darkly everything 👌 Thank you, for a quick fix 💪
Going to write some code (=
Is this a support request? This issue tracker is maintained by LaunchDarkly SDK developers and is intended for feedback on the SDK code. If you're not sure whether the problem you are having is specifically related to the SDK, or to the LaunchDarkly service overall, it may be more appropriate to contact the LaunchDarkly support team; they can help to investigate the problem and will consult the SDK team if necessary. You can submit a support request by going here and clicking "submit a request", or by emailing support@launchdarkly.com.
Note that issues filed on this issue tracker are publicly accessible. Do not provide any private account information on your issues. If your problem is specific to your account, you should submit a support request as described above.
Describe the bug
launchdarkly-react-client-sdk@2.16.0
was published with an emptylib/
folder, causing package managers to report it as a "missing dependency"To reproduce
launchdarkly-react-client-sdk@2.16.0
launchdarkly-react-client-sdk
lib/index.js
, which is not there in the 2.16.0 releaseExpected behavior
lib/
folder is populated with compiled sdk codeLogs
SDK version 2.16.0
Language version, developer tools Node v10.16.2
OS/platform PopOS 18.01
Additional context Add any other context about the problem here.