Skip to content

Releases: urql-graphql/urql

v1.1.0 – Server-side Rendering Support!

07 Jun 11:53
40cb2e0
Compare
Choose a tag to compare

After our recent announcement of urql v1 we've received lots of positive feedback and support, but it became clear that the most requested feature for urql was server-side rendering.

So we went back into the machine room and implemented it, so today we're publishing urql v1.1, just a week after our blog post! Our new implementation of server-side rendering works by adding a single new exchange, the ssrExchange, and using a new suspense-mode on the server-side, which can be used together with react-ssr-prepass to prefetch urql queries. 🎉

Getting started with server-side rendering in urql is easy! We've got an extensive guide on how to set it up, which you can read on our new & fancy docs site, or alternatively as markdown on GitHub.

We've also added a new example to our repository based on Next.js!

Changes

This version now also requires a version of React supporting hooks! (>= 16.8.0)
We unfortunately forgot to correct the peerDependencies entries in our v1.0.0 release.

  • ✨ Add server-side rendering support (see #268)
  • ✨ Ensure that state changes are applied immediately on mount (see #256)
  • Ensure that effects are run immediately on mount (see #250)
  • ⚠️ Remove create-react-context and bump React peer dependency (see #252)
  • Add generics to the Query, Mutation, and Subscription components
  • ⚠️ Fix issues where useQuery wouldn't update or teardown correctly (see #243)
  • ✨ Add support for pause prop/option to useQuery and Query (see #237)


v1.0.5

06 Jun 16:42
499c2f8
Compare
Choose a tag to compare
  • Export MutationProps types for TS typings, by @mxstbr (see #236)
  • Export Use*Args types for TS typings, by @mxstbr (see #235)
  • Export all hook response types for TS typings, by @good-idea (see #233)
  • ⚠ Fix runtime error in cachExchange where already deleted keys where being accessed (see #223)
  • ⚠️ Fix cacheExchange not forwarding teardowns correctly, which lead to unnecessary/outdated queries being executed, by @federicobadini (see #222)
  • Change GraphQLRequest to always pass on a parsed GraphQL DocumentNode instead of just a string, which reduces work (see #221)
  • Fix incorrect TS types by using Omit<T, K> (see #220)

v1.0.4

22 Feb 18:09
Compare
Choose a tag to compare
  • Fix __typename not being extracted from responses correctly, which broke caching
  • Fix fetchOptions being called in the client instead of the fetch exchange
  • Improve CombinedError to actually be an Error and rehydrate GraphQLError instances
  • Fix Mutation#executeMutation prop not accepting generics

v1.0.3

22 Feb 18:07
Compare
Choose a tag to compare
  • Fix variables not being diff'ed and only compared via reference equality leading to an infinite rerender bug

v1.0.2

22 Feb 18:06
Compare
Choose a tag to compare
  • Allow graphql-tag usage. Operations' querys can now be DocumentNodes
  • Query + Variables keying is now more optimised than before with more efficient hashing

v1.0.0 – Customisable & The one with hooks.

22 Feb 18:05
Compare
Choose a tag to compare

urql v1 is more customisable than ever with a concept of "exchanges", which allow you to customise every aspect of how urql works. Check out the docs for more info on v1!