Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Updating to 3.62.2 causes errors with `.default` properties

See original GitHub issue

General information

SDK version: 3.62.2
Environment: Sandbox
Browser and OS: Any

Issue description

Installing 3.62.2, compiled with rollup.js into our build, I get errors relating to package default imports:

Uncaught (in promise) TypeError: i.default is not a function
    emit framebus.js:45
    emit index.js:71
    _cleanUpFocusIntercepts hosted-fields.js:730
    removeExtraFocusElements focus-change.js:80
    removeExtraFocusElements focus-change.js:74
    _cleanUpFocusIntercepts hosted-fields.js:729
    HostedFields hosted-fields.js:623
    promise callback*HostedFields hosted-fields.js:617
    1 index.js:260
    promise callback*create$1 index.js:259
    wrapPromise wrap-promise.js:18
    createHostedFields payment-step.js:299  // Our code below here in this backtrace
    step_loaded payment-step.js:39
    CheckoutController checkout-controller.js:49
    _rollbar_wrapped rollbar.min.js:1
    dispatch checkout-step.js:39
    api_call checkout-step.js:179
    action_finish shipping-step.js:128
    CheckoutStep checkout-step.js:25
    _rollbar_wrapped rollbar.min.js:1
    o rollbar.min.js:2
    CheckoutStep checkout-step.js:20
    ShippingStep shipping-step.js:16
    execute shipping-step.js:152
    i system-core.js:274
    e system-core.js:270
    C system-core.js:219

Pardon the systemjs chaff here, but I think it provides context.

i.default in this case is the code referring to the framebus package, which is updated to version 4. Version 4 publishes some ESM-derived code that has a .default property on what’s returned from require — in some bundlers. With rollup, this is not the case and the code fails. Switching to esm-based modules is unfortunately a breaking change, it seems, with the state of the ecosystem.