-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Getting realm related error in console if using webpack.UglifyJsPlugin #1182
Comments
So, as far as I can see the problem is that |
So, I found how to avoid the issue:
option for |
Really sorry about this issue! I'm glad you were able to find a temporary work around, and I'm working on getting a new release out shortly that disables the check in mangled production bundles |
Thanks for sharing your diagnosis and debugging details. I found a similar conclusion which led to #1174. I'm going to close this issue since we have a fix that is release-ready |
Good day! graphql-js/src/type/directives.js Lines 19 to 22 in 740b7fa
I update my component MODX-Club/react-cms@80b111a#diff-1d00843fa6d5ebeccc3a828d9b30afea All project dependencies (but in node_modules only one graphql module) https://github.com/MODX-Club/ShopModxBox/blob/master/assets/components/modxsite/templates/shopmodx/v4.0/package-lock.json |
Closed? Getting the same error on
|
@scniro It's fixed in |
I am using |
@gferreri Did you specify |
That was indeed my problem. NODE_ENV was not set to `production`
…On Sat, May 12, 2018, 5:16 AM Ivan Goncharov ***@***.***> wrote:
I am using 0.13.2 and I still see this error.
@gferreri <https://github.com/gferreri> Did you specify production
enviroment to your bundler, here is how to do it for webpack:
https://webpack.js.org/guides/production/#specify-the-environment
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1182 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDyBr1REA1crjVRIaa4t2_IJ5HKcw0Tks5txqh9gaJpZM4RM-4j>
.
|
I wonder how the |
Working with Sapper and Temporarily fixed by building with |
Please re-open. Working with graphql on the client (with an RN project managed by expo) we don't have |
I don't believe that setting |
…ns. using workaround described here: graphql/graphql-js#1182 (comment) NODE_ENV=production
@croossin I was able to get rid of this issue by removing |
Hello,
I have a bit strange situation. If I build my project with UglifyJsPlugin I get this error:
I checked node_modules and I have only one
graphql
module installed and during development, I don't have this error. Moreover, my app still works fine and makes requests.When I debug
instanceOf
I see something like this:Any ideas what it could be and how to avoid it?
Versions:
Thanks, and btw, Happy New Year!
The text was updated successfully, but these errors were encountered: