-
Notifications
You must be signed in to change notification settings - Fork 12
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
Upgrading to 1.1.x causes a crash at runtime #7
Comments
Got the same error, I'm not using |
Sorry guys. Unintended side effect. Have to think about how to solve this so the package works in both GraphQl and non-GraphQL contexts. Short term work around would be to go back to 1.1.0 (only diff is that version doesn't support GraphQL), or install @nestjs/graphql. 😢 Sorry for not having a better answer right now. @igor-radivojevic-ct @tristan957 |
@johnbiundo I believe a way around this would be to dynamically load the graphql package using a similar technique which is discussed at nestjs/terminus#593 (comment). If you follow the line of code linked, maybe that could provide you with an idea. Thanks for your work. |
@tristan957 thanks for the pointer. I need to come back and spend some time on this, which will have to wait a bit due to some other current work. Thanks for your support. |
No problem. |
Should we rollback latest to 1.1.0? |
Looks like the dependency on the graphql package somehow bubbled up even when I am not using graphql in my project. I checked the package.json but I didn't see why this would happen.
The text was updated successfully, but these errors were encountered: