e2e Files

Minor Changes

• #790 0d1ed15 Thanks @okwasniewski! - Breaking: e2e and every @e2e-dev package now need Node.js 22.22.3 or newer on Node.js 22, or 24.8.0 or newer (engines.node is ^22.22.3 || >=24.8.0). Node.js 22.12 through 22.22.2, 23, and 24.0 through 24.7 are no longer supported, and the CLI refuses to start on them, naming the versions to upgrade to. Those releases fail when a CommonJS file a test imports requires TypeScript through the new loader's module.registerHooks (nodejs/node#59679 fixed it in 22.22.3 and 24.8.0).

e2e now loads TypeScript with its own loader, built on oxc, instead of tsx. tsx brought in esbuild, whose postinstall script made every pnpm install on pnpm 11 and later fail with ERR_PNPM_IGNORED_BUILDS until the project approved the build; nothing e2e installs runs an install script now. Config and tests load as before: ESM whatever package.json says, ./x.js and ./x resolve to x.ts and ./x.jsx to x.tsx, directory index imports, tsconfig paths and baseUrl, workspace packages exporting .ts source, JSX in .tsx and .jsx, enums, namespaces, experimentalDecorators, and source-mapped stack traces. JSON imported without with { type: 'json' } still loads. A test file whose name holds %, #, or a space now collects with its source location instead of failing with "URI malformed" or losing the location. Each file reads its nearest tsconfig.json rather than the one in the working directory. What changes: import statements in a .cts file are no longer compiled into require calls (write import x = require()); standard decorators without experimentalDecorators, auto-accessors, and ES module import and value export declarations in .cts are refused with their line (import type, export type, import x = require(), and export = work); the CLI refuses the Bun (bun --bun) and Deno runtimes (install with any package manager, run on Node.js); a type imported without import type that stays in the output (a decorated member's type under emitDecoratorMetadata) fails to load, with an error naming the import; a .ts file a CommonJS file requires runs as an ES module like every other .ts, so one written with module.exports needs the .cts extension; and an import written in a JavaScript file resolves as Node.js resolves it, without TypeScript's extension rules or tsconfig paths. TypeScript inside an installed package compiles without the project's tsconfig.json.