You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How are you deploying your application? (if relevant)
No response
Describe the Bug
when running mesh build on the latest @graphcommerce/[email protected] and @graphcommerce/[email protected] the cli throws an error on each graphqls schema:
💥 🕸️ Mesh Error: Directive "@injectable" already exists in the schema. It cannot be redefined.
Directive "@in...
ONLY when a single source is present in the .meshrc.yml config file
I realize this use case for graphql mesh is weird because it defeats its purpose, but we don't need graphcms in our project.
using the same source twice with a different name works for some reason
Expected Behavior
mesh building a single source
To Reproduce
remove graphcms source from .meshrc.yml, but it should throw the same error even if removing m2 source
The text was updated successfully, but these errors were encountered:
This might be due to a version mismatch between different packages, could you do a search through the node_modules/@graphcommerce folder for @Injectable and see if you find it multiple times?
This might be due to a version mismatch between different packages, could you do a search through the node_modules/@graphcommerce folder for @Injectable and see if you find it multiple times?
I can confirm you that "@Injectable" is not the problem, removing the declaration within node_modules simply moves the error to another schema declaration, anyway this issue can be reproduced on a clean working example
Provide environment information
v16.15.1
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
when running
mesh build
on the latest @graphcommerce/[email protected] and @graphcommerce/[email protected] the cli throws an error on each graphqls schema:ONLY when a single source is present in the .meshrc.yml config file
I realize this use case for graphql mesh is weird because it defeats its purpose, but we don't need graphcms in our project.
using the same source twice with a different name works for some reason
Expected Behavior
mesh building a single source
To Reproduce
remove graphcms source from .meshrc.yml, but it should throw the same error even if removing m2 source
The text was updated successfully, but these errors were encountered: