Andrzej Kiełtyka
Andrzej Kiełtyka
https://github.com/AndKiel/mikro-orm-nestjs-issue-128
Doesn't seem related. I have no issues with decorators in different projects using exactly the same ncc version and other dependencies but with sequelize instead mikro-orm. And `@mikro-orm/nestjs` v5.1.2 worked...
No, I mean exactly what I said above and I wrote the same in the issue description. `@mikro-orm/nestjs` v5.1.2 works. Upgrading to a higher version breaks built code execution.
I've added an alternative reproduction to the reproduction repository - one using `InjectRepository` instead of `EntityManager`. This variant throws the error even when using ts-node to execute the file. ---...
Ah, you're right, silly mistake. I fiddled with `scope` a bit and found out that: - If `scope` is not passed, using the `repository` throws `ValidationError`. More or less expected...
There are some edge cases around this. For example, if I make the whole MongoService in my reproduction have a scope but skip it in MikroOrmModule.forRootAsync, then I still get...
Perhaps the agent-base (and this repository) shouldn't use Node.js 14 types, as that version is EOL, and use at least v20 instead, keeping it up to date. https://github.com/TooTallNate/proxy-agents/issues/376
I tried upgrading to express v5 and it looks like apollo-server is incompatible. This check: https://github.com/apollographql/apollo-server/blob/597f6e1cb7abc65282737ff46d3c008bc8384c25/packages/server/src/express4/index.ts#L47 is invalid because of the following breaking change: > The req.body property returns undefined...
When the `req.body` check is removed from `expressMiddleware`, my API seems to work fine, including a route configured after the `ApolloServer` (otherwise, the `req.body` check would prevent it from executing)....
For anyone interested in the cleaned-up middleware (`req.body` check removed etc.) express-middleware.ts ```typescript import { ApolloServer, BaseContext, ContextFunction, HeaderMap } from "@apollo/server"; import type { Request, RequestHandler, Response } from...