[V1] Object at path is not a service constructor (only last added grpc service is ran correctly)

[Justin-Booij]

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

• 1. The issue provides a reproduction available on
  Github,
  Stackblitz
  or
  CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

graphql-mesh will only run the last, alphabetical, service correctly in v1 for GRPC services. Any other service will error with the message Object at path xx.xxService is not a Service constructor

To Reproduce Steps to reproduce the behavior:

see: reproduction repository

1. start store-api and pet-api using node node api.js f.e on both api's
2. run npm run start in the main directory
3. go to localhost:4000/graphql
4. Try doing both GetAllPets and GetAllPetStores, this will return all petstores but error on petservice
5. Rename the "Stores" service in mesh.config.ts to "AStores"
6. restart & rebuild the mesh service
7. retry step 4, this time the petstore will error with the same message

Expected behavior

Every grpc service to properly be approachable through graphql-mesh

Environment:

• OS: Linux fedora & docker (linux)
  -Packages:
  "@graphql-hive/gateway": "^1.4.10",
  "@graphql-mesh/compose-cli": "^1.1.9",
  "@graphql-mesh/transport-grpc": "^0.0.1",
  "@omnigraph/grpc": "^0.1.1",
  "@omnigraph/openapi": "^0.107.5",
• Grpc (both using node server and c# servers