Jest tests started failing with jose ESM issue after v1.13.0

[aldenquimby]

We recently tried upgrading from v1.12.1 to latest, but all of our jest tests started failing with this error:

We are on jest 30.1.3 (effectively latest) and use @swc/jest to build/run. If I revert #124 then our tests pass again. Any ideas what might be going on here? I didn't see anything major in the release notes, and since this is a minor version upgrade I wouldn't expect breaks. Thanks for the help

[linear]

KNO-9725 Jest tests started failing with jose ESM issue after v1.13.0

[mattmikolay]

Hi @aldenquimby. Can you try updating your Jest config to add the following?

{
  transformIgnorePatterns: [
    // jose needs to be transformed because it's only ESM
    '/node_modules/(?!jose)',
  ],
}

Our Node SDK uses jose to sign JWTs. The latest releases of jose are ESM-only.

#124 made it so that jose is imported statically rather than dynamically, and given Jest’s support for ESM is still experimental, you may need to update your Jest config to make it play nicely with jose.

Alternatively, you could try running Jest with one of the following:

node --experimental-vm-modules node_modules/jest/bin/jest.js

yarn node --experimental-vm-modules $(yarn bin jest)

[aldenquimby]

Ok I'll give that a try, thanks! Out of curiosity, what's the benefit of importing statically over dynamically? It's kind of a bummer if using knock-node requires all consumers to modify jest configs

[mattmikolay]

We previously imported jose dynamically because it used to be an optional peer dependency. (#109 made it so that jose is a standard dependency.) We switched to a static import because some of our customers were encountering issues with the dynamic import.

[aldenquimby]

@mattmikolay update transformIgnorePatterns fixed the issue for us ✅