@everystack/server 0.2.23 → 0.2.26

package/jest-preset.js

@@ -1,32 +1,60 @@
 /**
- * @everystack/server/jest-preset — drop-in jest config for a consumer's
- * server-boundary test project (the one that imports `@everystack/server/testing`).
+ * Drop-in jest config for a consumer's server-boundary test project (the one
+ * that imports `@everystack/server/testing`).
  *
  *   // jest.config.js
- *   module.exports = { preset: '@everystack/server/jest-preset' };
+ *   module.exports = { preset: '@everystack/server' };
+ *
+ * Note the value is the package name, NOT '@everystack/server/jest-preset':
+ * jest appends `/jest-preset.js` to the preset string itself, so it resolves
+ * this file as `@everystack/server/jest-preset.js`.
+ *
+ * IMPORTANT — this preset OWNS `transform`. Jest gives your config precedence on
+ * shared keys, so if your jest config also defines `transform`, it REPLACES the
+ * ts-jest block below and the explicit `@everystack/server/testing` pin is lost.
+ * A dedicated server-boundary project should set only
+ * `{ preset: '@everystack/server' }` (plus non-transform keys). If you must
+ * customize, spread this preset and leave `transform`/`moduleNameMapper` alone:
+ *   const p = require('@everystack/server/jest-preset');
+ *   module.exports = { ...p, testTimeout: 30000 };
  *
  * Why a preset is needed
  * ----------------------
- * @everystack packages ship TypeScript source, and their subpaths (like
- * `@everystack/server/testing`) are reachable only through the package
- * `exports` map. Two things have to be true for a consumer to import them:
- *
- *  1. TypeScript must read the `exports` map. Only `node16`/`nodenext`/`bundler`
- *     resolution does. ts-jest under `module: commonjs` silently falls back to
- *     classic `node` resolution, which ignores `exports` → TS2307. NodeNext is
- *     the one mode that reads `exports` AND emits CommonJS for jest. Its hybrid
- *     module kind makes ts-jest warn TS151002; we silence only that one code
- *     (NOT via `isolatedModules: true`, which would switch ts-jest to
- *     transpile-only and drop type-checking entirely).
+ * @everystack ships TypeScript source, and `@everystack/server/testing` is a
+ * subpath reachable only through the package `exports` map. ts-jest's resolution
+ * of that subpath is unreliable on a COLD cache (fresh CI, `jest --no-cache`):
+ * it intermittently fails to read the exports map and throws
+ * `TS2307: Cannot find module '@everystack/server/testing'` — passing only once a
+ * warm cache exists, so it's green locally and red in CI. Flattening the export
+ * target does not fix it; an explicit pin does.
  *
- *  2. jest must TRANSFORM the shipped `.ts` source. Source in `node_modules` is
- *     ignored by default, so the `transformIgnorePatterns` allowlist below opts
- *     `@everystack/*` back in. (Inside this monorepo the pnpm symlink escapes
- *     `node_modules` and hides this requirement — real installs need it.)
+ * So this preset resolves its OWN testing entry from disk (below) and pins it two
+ * ways, both cache-independent:
+ *   - tsconfig `paths`        → the type-checker resolves it deterministically.
+ *   - `moduleNameMapper`      → the jest runtime resolves it deterministically.
+ * It also opts `@everystack/*` back into transformation (source ships as `.ts`,
+ * and `node_modules` is not transformed by default).
  *
  * Requires `ts-jest` and `typescript` in the consuming project (already present
  * for any TS jest setup).
  */
+const path = require('path');
+const fs = require('fs');
+
+// Resolve this package's `testing` entry from the preset's own location, so the
+// pin points at a real file regardless of layout (flat src/testing.ts or nested
+// src/testing/index.ts) or where the package is installed.
+const TESTING_ENTRY = ['src/testing.ts', 'src/testing/index.ts']
+  .map((rel) => path.join(__dirname, rel))
+  .find((abs) => fs.existsSync(abs));
+
+const testingPin = TESTING_ENTRY
+  ? { '@everystack/server/testing': [TESTING_ENTRY] }
+  : {};
+const testingMapper = TESTING_ENTRY
+  ? { '^@everystack/server/testing$': TESTING_ENTRY }
+  : {};
+
 module.exports = {
   testEnvironment: 'node',
   moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
@@ -42,6 +70,9 @@ module.exports = {
           esModuleInterop: true,
           skipLibCheck: true,
           types: ['jest', 'node'],
+          baseUrl: __dirname,
+          // Pin the exports subpath so the type-checker resolves it cold.
+          paths: testingPin,
         },
         // 151002: "hybrid module kind needs isolatedModules" — expected under
         // NodeNext; suppressing it keeps full type-checking on (real type errors
@@ -52,8 +83,10 @@ module.exports = {
   },
   // @everystack packages ship source, not built dist — transform them.
   transformIgnorePatterns: ['/node_modules/(?!@everystack/)'],
-  // NodeNext consumers may write `.js` on relative ESM specifiers; map to source.
   moduleNameMapper: {
+    // Pin the exports subpath so the jest runtime resolves it cold.
+    ...testingMapper,
+    // NodeNext consumers may write `.js` on relative ESM specifiers; map to source.
     '^(\\.{1,2}/.*)\\.js$': '$1',
   },
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/server",
-  "version": "0.2.23",
+  "version": "0.2.26",
   "description": "Server runtime primitives for Lambda — event adapters, routing, SSR, image processing",
   "license": "AGPL-3.0-only",
   "author": "Scalable Technology, Inc. <licensing@scalable.technology>",