LogRocket incident

SDK breaking lodash on some sites

Major Resolved View vendor source →

LogRocket experienced a major incident on July 12, 2021, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 12, 2021, 02:20 PM UTC
Resolved
Jul 12, 2021, 02:20 PM UTC
Duration
Detected by Pingoru
Jul 12, 2021, 02:20 PM UTC

Update timeline

  1. resolved Jul 19, 2021, 03:47 PM UTC

    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.

  2. postmortem Jul 19, 2021, 03:49 PM UTC

    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