The @nestjs/* packages installed from npm (graphql, apollo, mongoose,
typeorm) import @nestjs/core and @nestjs/common from where they are
installed. When node_modules is linked to another checkout, as in a git
worktree that shares the main checkout's node_modules, that is a second
copy of every class. Dependency injection then failed (GraphQLModule
could not resolve HttpAdapterHost), so every graphql-schema-first spec
failed in such a checkout while CI passed.
The integration config now dedupes the packages of this repository, so
Vite resolves them from the project root whoever imports them. Nothing
changes where node_modules is installed in place.
- These suites failed with two copies of `ModuleRef` and `HttpAdapterHost`: the tests import
`@nestjs/core` from its TypeScript sources, while the `@nestjs/*` packages in node_modules
loaded the compiled build.
- Inline `@nestjs/apollo`, `graphql`, `mongoose` and `typeorm` so their core imports resolve to
the same sources, and remove the three exclusions.
- Replace the outdated CommonJS note with the reason each remaining suite stays excluded.
Kamil Myśliwiec