test/jest-e2e.json listed the ESM-only packages ts-jest must still transform, but @nestjs/schedule (12.0.1, "type": "module") was not among them. Since AppModule imports ScheduleModule for the backup scheduler, every e2e spec died on "SyntaxError: Unexpected token 'export'" while loading AppModule - the whole suite, not one test. That silently disabled test/authorization-coverage.e2e-spec.ts, the check that asserts every non-public route carries @RequirePermission or @AnyAuthenticatedUser. It is exactly the check that would have caught the displaced decorators fixed in the previous commit, and it had been dead since the scheduler shipped. With @nestjs/schedule and its cron dependencies added to the allowlist, the authorization-coverage spec compiles and passes, confirming no route is left undecorated. The remaining 36 e2e specs still need a Postgres instance on the port .env.test points at; they fail on connection, not on code. Co-Authored-By: Claude Opus 5 <[email protected]>
15 lines
403 B
JSON
15 lines
403 B
JSON
{
|
|
"moduleFileExtensions": ["js", "json", "ts"],
|
|
"rootDir": ".",
|
|
"testEnvironment": "node",
|
|
"testRegex": ".e2e-spec.ts$",
|
|
"setupFiles": ["<rootDir>/setup-env.ts"],
|
|
"maxWorkers": 4,
|
|
"transform": {
|
|
"^.+\\.(t|j)s$": "ts-jest"
|
|
},
|
|
"transformIgnorePatterns": [
|
|
"node_modules/(?!(otplib|@otplib|@scure|@noble|openid-client|oauth4webapi|jose|@nestjs/schedule|cron|croner|uuid)/)"
|
|
]
|
|
}
|