From 07692db4e0bb8823c33f8c410d3d9b2294603bc4 Mon Sep 17 00:00:00 2001 From: Nicolas Date: Sun, 16 Aug 2026 10:51:58 +0200 Subject: [PATCH] Fix Cypress config loading: give the solution tsconfig a module system MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit apps/web/tsconfig.json (the tsc -b "solution" file) had no compilerOptions, only files/references. Cypress's bundled ts-node picks the nearest tsconfig.json to transpile cypress.config.ts, and with no "module" specified it defaulted to CommonJS while package.json declares "type": "module" — causing: ReferenceError: exports is not defined in ES module scope Adding module/moduleResolution to the solution config (harmless for tsc -b itself, since it only builds the referenced projects) fixes the mismatch. This regressed after the earlier fix for the stray vite.config.js emission and was never re-verified against Cypress until CI caught it. --- apps/web/tsconfig.json | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/apps/web/tsconfig.json b/apps/web/tsconfig.json index d32ff68..558996e 100644 --- a/apps/web/tsconfig.json +++ b/apps/web/tsconfig.json @@ -1,4 +1,8 @@ { + "compilerOptions": { + "module": "ESNext", + "moduleResolution": "Bundler" + }, "files": [], "references": [{ "path": "./tsconfig.app.json" }, { "path": "./tsconfig.node.json" }] }