Changes / LogRocket / SDK breaking lodash on some sites
LogRocket: Major incident: SDK breaking lodash on some sites
Summary
Summary pending. The diff below shows exactly what changed.
What changed
Before: not present
After: SDK breaking lodash on some sites
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2021-07-12 14:20 UTC
Before: not present
After: 2021-07-12 14:20 UTC
Before: not present
After: 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.
Before: not present
After: 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
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: SDK breaking lodash on some sites (this change) | Major incident |
All LogRocket changes → · LogRocket profile · Markdown · JSON