@open-mercato/channel-gmail 0.7.1-develop.7173.1.a901520d0f → 0.7.1-develop.7175.1.d49ab48ee2

package/jest.config.cjs

@@ -6,6 +6,7 @@ module.exports = {
   testEnvironment: 'node',
   watchman: false,
   rootDir: '.',
+  setupFilesAfterEnv: ['<rootDir>/jest.setup.ts'],
   moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json'],
   moduleNameMapper: {
     '^@open-mercato/channel-gmail/(.*)$': '<rootDir>/src/$1',

package/jest.setup.ts

@@ -0,0 +1,22 @@
+/**
+ * Warm the lazy `mailparser` import before any test body runs (#6040).
+ *
+ * `normalizeInboundGmailMessage` resolves `mailparser` lazily, inside the
+ * function, so the whole cold module-graph load is charged to whichever test
+ * first reaches it — against jest's default 5000 ms per-test budget. On a
+ * contended CI runner that load alone approaches the timeout, which made the
+ * first MIME-parsing test in a file fail intermittently while every sibling
+ * passed.
+ *
+ * Paying the load in a root `beforeAll` with an explicit, generous hook budget
+ * removes it from every test's budget without raising `testTimeout`, so a
+ * genuinely slow adapter regression still trips the 5000 ms default.
+ *
+ * Wired package-wide rather than per test file because it measures free — full
+ * suite 1.04 s → 1.01 s, i.e. noise, since suites run on two workers and the
+ * loads overlap — and it covers every future test file without anyone having
+ * to remember the hook.
+ */
+beforeAll(async () => {
+  await import('mailparser')
+}, 60_000)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-mercato/channel-gmail",
-  "version": "0.7.1-develop.7173.1.a901520d0f",
+  "version": "0.7.1-develop.7175.1.d49ab48ee2",
   "license": "MIT",
   "type": "module",
   "main": "./dist/index.js",
@@ -62,19 +62,19 @@
     }
   },
   "dependencies": {
-    "@open-mercato/core": "0.7.1-develop.7173.1.a901520d0f",
-    "@open-mercato/ui": "0.7.1-develop.7173.1.a901520d0f",
+    "@open-mercato/core": "0.7.1-develop.7175.1.d49ab48ee2",
+    "@open-mercato/ui": "0.7.1-develop.7175.1.d49ab48ee2",
     "@types/mailparser": "^3.4.5",
     "mailparser": "^3.9.17"
   },
   "peerDependencies": {
     "@mikro-orm/postgresql": "^7.0.14",
-    "@open-mercato/shared": "0.7.1-develop.7173.1.a901520d0f",
+    "@open-mercato/shared": "0.7.1-develop.7175.1.d49ab48ee2",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
   },
   "devDependencies": {
-    "@open-mercato/shared": "0.7.1-develop.7173.1.a901520d0f",
+    "@open-mercato/shared": "0.7.1-develop.7175.1.d49ab48ee2",
     "@types/jest": "^30.0.0",
     "@types/react": "^19.2.18",
     "@types/react-dom": "^19.2.5",

package/src/modules/channel_gmail/lib/__tests__/mailparser-warmup.test.ts

@@ -0,0 +1,25 @@
+/**
+ * mailparser warm-up guard (#6040).
+ *
+ * `normalizeInboundGmailMessage` resolves `mailparser` lazily, inside the
+ * function. Without the root warm-up in `jest.setup.ts` the cold module-graph
+ * load therefore lands inside whichever test first parses a MIME message, and
+ * competes with jest's default 5000 ms per-test budget — which is what made
+ * three tests fail intermittently on CI while every sibling passed.
+ *
+ * Jest gives every test file its own module registry, and `require.cache`
+ * reflects that registry. This file imports nothing, so an entry for
+ * `mailparser` can only have been put there by the warm-up — making it a direct
+ * observation of the property the flaky tests depend on, rather than a timing
+ * assertion that would itself be flaky.
+ *
+ * Note this reads the CommonJS registry, which is what ts-jest's transform
+ * produces today. Should that ever emit native ESM dynamic imports, the
+ * warm-up would still work but this assertion would need rewriting — it fails
+ * closed, so the breakage is loud rather than silent.
+ */
+describe('mailparser warm-up', () => {
+  it('resolves mailparser before any test body runs', () => {
+    expect(require.cache[require.resolve('mailparser')]).toBeDefined()
+  })
+})