I’m trying to import some backend methods apps/backend/...
into my packages/graphql
because my graphql resolvers actualy calls backend routes, but I can’t seem to see how in turbo monorepo documentation…
my current frontend (client
) imports "@repo/graphql" : "*"
but now i need my graphql package to access my backend (server
) methods, but I can’t just workaround that with relative path, because turbo will not resolve it after deployment.
does anyone have an idea ?
would you recommand me to have graphql as an app in /apps
or the packages strategy is a good idea perhaps ?
here is somme information:
let’s say I have a getComment
from my ./apps/server/src/domain/task/comment.controller.ts
and that I access that ressource through graphql ./packages/graphql/graphql/src/resolvers.ts
, the resolver would call that specific method.
.
├── apps
│ ├── client
│ └── server
├── packages
│ ├── graphql
│ │ ├── graphql
│ │ │ ├── schema.gql
│ │ │ ├── resolvers.ts
│ │ │ └── src
│ │ ├── package.json
│ │ ├── src
│ │ │ ├── schema.graphql
│ │ │ └── server.ts
│ │ ├── README.md
│ │ ├── codegen.yml
│ │ └── tsconfig.json
│ └── prisma
├── README.md
├── docker-compose.yml
├── eslint.config.mjs
├── makefile
├── package-lock.json
├── package.json
├── prettier.config.mjs
├── tsconfig.json
└── turbo.json