tool · inferred from evidence
Jest
A JavaScript testing framework mentioned as the environment where the module resolution failure occurs.
- Prisma Memory Leak when using in NestJS app, reported by Jest
If you see memory issues with Prisma in NestJS tests, upgrade to Node.js 18 or newer; that solved it for the reporters. Also make sure every test suite calls prisma.$disconnect (or app.close) so Prisma cleans up its resources.
- Doesn't work with Jest
[dgraham (maintainer)]: If @planetscale/database fails to import under Jest with "unexpected token" parse errors, upgrade to the 1.9.0 release or newer: it ships a CommonJS build that Jest can parse.
- Pulumi Automation API up fails with SyntaxError after provisioning everything
This was a bug in the Automation API's output handling during preview, fixed upstream in PR #20824 and shipped in Pulumi v3.206.0. Upgrade the Pulumi CLI (and the Automation API package) to v3.206.0 or later and the intermittent SyntaxError
- Cannot find module './auth.js' from 'node_modules/@vonage/auth/dist/cjs/index.cjs'
A September release shipped a misconfigured TypeScript build / package.json exports map, so the ESM/CJS entry points referenced built files (e.g. `./auth.js`) that were not emitted. Workaround that was shared: `npm cache clean --force` and
- Jest fails with Cannot find module 'fastly:secret-store' for Fastly Compute@Edge app
Use the jest preset ysugimoto/jest-preset-fastly-js-compute in your jest config: it maps fastly: namespaced imports to local mocks so tests can run outside the Compute@Edge runtime. This is the integration Fastly's own maintainer recommends