Closed njlg closed 2 years ago
Unfortunately there's a problem with that dependency update, which is why we have deliberately not updated js-client-sdk or react-client-sdk to include it yet. We need to revisit it so thanks for this reminder, but we can't simply bump the dependency at the moment.
Dang! I get tired of seeing these messages:
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
:)
I know. I wish I could remember what the problem was that we ran into, but I can't find it offhand - I'm sure it will show up again if I go back and try to do the update again. I believe it had something to do with the newer package not being quite as browser-compatible as it claimed to be— possibly relying on some Node dependency— it may have been a misunderstanding on our part but it did seem like some changes would be required other than just bumping the version.
The
js-sdk-common
package got bumped to include a newer version ofuuid
(see https://github.com/launchdarkly/js-sdk-common/issues/46). Can we bump this package and include a newer version ofuuid
andjs-sdk-common
?