Skip to content
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

exchange-graphcache: 2.3.4: Uncaught TypeError: y is not a function #723

Closed
frederikhors opened this issue Apr 20, 2020 · 9 comments · Fixed by #726
Closed

exchange-graphcache: 2.3.4: Uncaught TypeError: y is not a function #723

frederikhors opened this issue Apr 20, 2020 · 9 comments · Fixed by #726
Labels
bug 🐛 Oh no! A bug or unintented behaviour.

Comments

@frederikhors
Copy link
Contributor

@urql/exchange-graphcache: 2.3.4

Just updated from 2.3.3 and BOOM! 💥

image

image

Updates follow.

@frederikhors frederikhors added the bug 🐛 Oh no! A bug or unintented behaviour. label Apr 20, 2020
@frederikhors
Copy link
Contributor Author

@JoviDeCroock
Copy link
Collaborator

You'll have to update @urql/core and it won't be an issue

@frederikhors
Copy link
Contributor Author

OK. So I think also here we need a change: https://github.com/FormidableLabs/urql/blob/master/packages/svelte-urql/package.json, right?

@JoviDeCroock
Copy link
Collaborator

Yes, thought it would've done this automatically but it just turns out it didn't

@frederikhors
Copy link
Contributor Author

Yes, me too. Because of "@urql/core": "^1.10.8",. I'm reinstalling all in my project now to try.

@frederikhors
Copy link
Contributor Author

frederikhors commented Apr 20, 2020

After re-install it works and in package-lock I can see new core. I hate npm. Thanks anyway. 😄

@JoviDeCroock
Copy link
Collaborator

Thanks for making us aware of this and have a nice day :)

@frederikhors
Copy link
Contributor Author

frederikhors commented Apr 20, 2020

Maybe we should reopen this to update @urql/svelte package.json?

Codesandbox is broken e.g..

@kitten
Copy link
Member

kitten commented Apr 21, 2020

Sorry about this! I finally found what caused our broken builds and #734 fixed it. That's released as @urql/[email protected] and @urql/[email protected]. The broken releases have been marked as deprecated (or deleted where possible) on npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Oh no! A bug or unintented behaviour.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants