-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing a Module
reference to module throws Error
#2476
Comments
I ran into this one as well. Thank you for the fix, @justin-equi! Works great. My environment has node 22.11.0, My reproduction is similar to what's posted above. Difference is I'm passing arrays to If anyone else winds up here before the fix is merged, here's the generated patch-package file I'm using. I don't know if it's exactly what Justin did there, but it got rid of the error for me, and everything seems to work fine.... so far :) file
|
Describe the bug
Some build systems do not expose prototype on Module, so when a caller passes a direct module interface into the module it blows up. I believe this is the actual correct behaviour for the Module object. I ran into this issue with a vitest setup. Seems unlikely this is the only situation where this might be an issue.
Example
And then the caller sets up the module as following
Will fail with
TypeError: currentResolvers.hasOwnProperty is not a function
at mergeResolvers (file:///.node_modules/graphql-modules/index.mjs:1694:34)
at createResolvers (file://./node_modules/graphql-modules/index.mjs:1584:43)
at Object.factory (file:///./node_modules/graphql-modules/index.mjs:1971:40)
at file:///./node_modules/graphql-modules/index.mjs:1273:57
Fixes # (issue)
To Reproduce
Steps to reproduce the behavior:
//here is a repo that reproduces
https://github.com/jspears/graphql-modules-module-bug
Expected behavior
To not throw error
Environment:
@graphql-modules/graphql-modules
:Additional context
The text was updated successfully, but these errors were encountered: