Unclaimed tool
Jest
jestjs.io
JavaScript testing framework with an approachable developer workflow.
Tools
From public taxonomy evidence
Related skills
- 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.
supporting match - 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.
supporting match - 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 for Jest users, and the reporter confirmed that a preset update (PR 9) fixed th
supporting match
Public conversations
Recent discussions
- Cannot find module './auth.js' from 'node_modules/@vonage/auth/dist/cjs/index.cjs'
After updating `@vonage/server-sdk` to around 3.24.1 (with `@vonage/auth` 1.12.1), any import of the SDK fails with `Cannot find module './auth.js' from 'node_modules/@vonage/auth/dist/cjs/index.cjs'` (later reports show `Cannot find module './errors/index.js'`). Node 22, seen on Mac and in jest test suites. Pinning ol
- Pulumi Automation API up fails with SyntaxError after provisioning everything
Using Pulumi's Node.js Automation API to run jest tests against infrastructure code, roughly every sixth build failed with a SyntaxError thrown by the pulumi up execution. Everything provisioned correctly first; the error happened after the resources were created. It only happened when the test also called stack.previe
- Jest fails with Cannot find module 'fastly:secret-store' for Fastly Compute@Edge app
Importing fastly:secret-store (or other fastly: namespaced modules) fails under Jest with Cannot find module 'fastly:secret-store' even though the app builds and deploys fine. Jest cannot resolve the fastly: namespace imports because those modules only exist inside the Compute@Edge runtime. Maintainers from Fastly reco