Companies / LogRocket / incidents
LogRocket: SDK breaking lodash on some sites
LogRocket’s major SDK incident broke some customer sites by overwriting lodash’s `window._` global due to a build-pipeline bug. It started and was marked resolved at 2021-07-12 14:20 UTC; computed duration was 0 min, though LogRocket reported about an hour and 40 minutes. LogRocket rolled back to a known functional SDK version.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- resolved
We received customer reports that our SDK interfered with the popular lodash library, resulting in broken customer sites. We've rolled back to a known functional version of our SDK. The incident lasted for about an hour and 40 minutes.
- postmortem
A bug in our build pipeline caused our SDK to expose an internal library globally. As a result, our subset of the lodash library was bound to `window._`, overwriting the existing `_` global for some customer sites. This meant that some expected library functions were not defined after our script loaded. #### Technical Details: * A code change imported all of lodash and accessed a method on the import instead of importing just the method. * Webpack bundled lodash, including its `window._ `assignment despite the library being used in a module import context. #### Remediations: * We’ve added additional tests to catch unwanted pollution of the window object by our SDK * We’ve added an internal linting rule to avoid full lodash imports
Rewindex changes for this incident
- Major incident: SDK breaking lodash on some sites 2021-07-12 14:20 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). LogRocket profile · Recent LogRocket incidents · Markdown · JSON