-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Unexpected String with graphql package #16060
Comments
Hi @idc77! 👋 It looks like you provided an invalid or unsupported reproduction URL. Without a proper reproduction, your issue will have to get closed. Thank you for your collaboration. 👏 |
See #14077 |
I am having the same issue. I can't seem to get rid of it. What was the solution? |
same error from here :( |
See my solution here: graphql/graphql-js#3919 (comment) |
Here is my solution: Set
|
Thanks, this worked well for me |
can confirm this works, has solved my issue as well! |
Not a solution for me! |
@WulfP use build: {
rawDefine: {
'globalThis.process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)
}
} |
thanks! it work |
thank you. rawdefine worked (because I have stuff in .env) Let's hope this has no long-term implications. |
Here is my solution, it can keep old env extendViteConf(viteConf) {
viteConf.define['globalThis.process.env.NODE_ENV'] =
viteConf.define['process.env.NODE_ENV'];
return viteConf;
}, |
this one solved mine
|
What happened?
Please see graphql/graphql-js#3919
What did you expect to happen?
No error
Reproduction URL
N/A
How to reproduce?
not sure
have graphql package >16.6.0 installed I guess, from what I gather in the Nuxt issue
when I downgraded to 16.6.0 the error went away.
I don't know how to force quasar to use Vite v4.
How do I upgrade to Vite v4?
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)
Platforms/Browsers
No response
Quasar info output
Relevant log output
Additional context
using quasar with apollo graphql client
The text was updated successfully, but these errors were encountered: