-
Notifications
You must be signed in to change notification settings - Fork 55
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
Updated to 0.3.5 produced critical failure #103
Comments
Please create a repro example. |
Facing the same issue. Any update? |
I'm running 0.3.5 in production without any issues, so there must be something different about your setup. @RiyazMemon Can you create a reproduction? |
Hey @shawnmcknight, Thanks for a quick response. I have created a new project using a typescript template (https://github.com/moleculerjs/moleculer-template-project-typescript) and installed npm package moleculer-apollo-server. Followed the usage instruction (https://github.com/moleculerjs/moleculer-apollo-server#usage) and tried running it then I got this error. |
@RiyazMemon I'm running the example from this repo ( |
I got this issue fixed by downgrading my node version. (now it is 14.XX. It was 17.XX earlier) CC: @shawnmcknight |
OK, I can replicate the problem on Node On
I'm assuming that node 17 has dropped support whatever is generating that deprecation warning. jaydenseric/extract-files#30 is a reference issue for the issue in the
A big problem here is that versions of |
Adding the following to
Note: The However, I also noticed that the test suite for |
See the error message in graphql @shawnmcknight
This run-time error occurs after bumping the revision in package.json.
The text was updated successfully, but these errors were encountered: