graphql-mesh support

[nemonemi]

Description

When generating an application, it should be possible to generate one which provides graphql-mesh out of the box.

Motivation

At the moment, it is only possible to generate, for an example @nrwl/node application, and then to reconfigure it to support something else, which is not directly nodejs.

This is also somewhat fine, however, I am not sure how to completely configure it so that such an application can be integrated with NX.
For example, what should be the content of the <app>.architect.serve?

"serve": {
  "builder": "@nrwl/node:execute",
  "options": {
    "buildTarget": "bd-api:build"
  }
},

This is the configuration that gets rendered. How should this look like?

Suggested Implementation

Provide a generator for the graphql-mesh.
Document on how to go about it without the generator.

[github-actions]

This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[nemonemi]

While there hasn't been much action on this ticket, I'd propose not closing it.

[AgentEnder]

There's a community plugin that should help with this some: #9987

Im going to close this out as there hasn't been much activity on it, and we don't have plans to introduce first-party support in our generators.

[ThePlenkov]

By the way - i don't know does it make sense or not. But i have a similar problem - that my *.ts schema was not able to load because of not resolved internal dependency. So what i did is quite simple:

added this part to a root package.json + npm install

"workspaces": [
    "packages/*"
  ]

it will create symlinks to your packages in root node_modules

and also I had to add "main":"src/index" to each of package's package.json

Right after this mesh dev/serve works right from your package even dependency is not maintained.

So using executor is not really needed.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.