When using the LaunchDarkly component in a universal app, the rendering of LaunchDarkly may occur server-side. This poses a problem since ldclient-js is only for the browser. It uses XMLHttpRequest which is not available in node. For reference, this wasn't an issue prior to 0.0.9. However, in 0.0.9, we moved the client initialization into the LaunchDarkly component.
Solution
Moving the initialization of the client into the FeatureFlag component, we can ensure that the LaunchDarkly component can continue to be used at the top-most level in your component hierarchy.
Problem
When using the
LaunchDarklycomponent in a universal app, the rendering ofLaunchDarklymay occur server-side. This poses a problem sinceldclient-jsis only for the browser. It usesXMLHttpRequestwhich is not available in node. For reference, this wasn't an issue prior to 0.0.9. However, in 0.0.9, we moved the client initialization into theLaunchDarklycomponent.Solution
Moving the initialization of the client into the
FeatureFlagcomponent, we can ensure that theLaunchDarklycomponent can continue to be used at the top-most level in your component hierarchy.