Avoid type duplication in a monorepo project

[minox86]

I'm trying a configure an enterprise monorepo and multi-package Typescript project that use graphql-code-generator. My (simplified) project structure is the following:

packages/
       core/
            src/ 
                    typedefs.ts (containing all model types of the schema in a graphql-tag)
                    types.generated.ts
            codegen.yml
            package.json
       api/
            src/ 
                    operations.ts (containing inputs, queries and mutations in a graphql-tag)
                    types.generated.ts
                    resolvers.generated.ts
            codegen.yml
            package.json
package.json

What we would like to achieve is simply to generate all types related to models in the core package, where we'll also develop the data access layer and some logics, and to generate resolvers and only inputs and operation related types in the api package.

My problem is substantially that I need to add typedefs from the core package in the api codegen (because queries and mutations relies on them), but I would not like to to generate them in the api package, because it already picks them from its dependency to the core package.

Any idea about this? Someone with the same problem?

[minox86]

Nobody with similar problems? @dotansimha