-
Notifications
You must be signed in to change notification settings - Fork 347
Cannot read property 'delete' of undefined #986
Comments
I'm seeing this as well. |
Yup seeing this too |
Same here... |
As a workaround
Check older version of apollo-link-dedup was installed |
@dinidu01 this is the first time I see that "resolutions" key in use. Would you mind explaining why this works? Couldn't I just pin the version of the package to |
That means that your subscribers are undefined, anything specific you did to achieve this? |
@JoviDeCroock for me it happened magically over night without me changing any code. I suspect there is a bug in the zen-observable release that was released 5 hours ago. |
Same here, I debug it and found the missing key is an @client query |
This is a mistake I think, so we get a subscriber and call |
same here
|
Same here. Breaking our builds. |
Same here :( |
same here, take me couple hours to figure it out from cicd flow :( |
Let's not keep reacting Sorry for the inconvenience, we'll work actively to fix this asap. |
|
@mbrochh No, you couldn't. In this case y'll have more that one package with different versions. Try
With "resolutions" you got one package (on install after remove node_modules). |
A fix for this is coming momentarily - sorry for the headache all! |
Just a heads up about |
Awesome, thanks for such quick fix guys! |
Unfortunately, after upgrading my dependencies, I'm still seeing this error, although with a slightly different stack trace. It seems to appear after every query. My dependencies are:
The stack trace is:
|
Try adding: "resolutions": { |
Thanks @JoviDeCroock! That did the trick. For anyone who runs into this in the future before 2.6, a summary of the fix:
This will resolve the apollo-link-dedup dependency within Apollo Client (currently at |
One of your dependencies is pulling |
It seems like it was apollo client itself. Running
|
After upgrade to apollo-link-dedup@1.0.17 got errors.
The text was updated successfully, but these errors were encountered: