The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
MIT License
Bot releases are hidden (Show)
We urgently recommend all users of the React bindings to upgrade to this patch!
Please don't forget to deduplicate your installed version of @urql/core
after you upgrade.
setState
) may recursively schedule a mount, which then disabled other setState
updates from being processed. Previously we assumed that React used a trampoline scheduler for updates, however it appears that setState
can recursively start more React work, by @kitten (See #2556)We urgently recommend all users of the React bindings to upgrade to this patch!
Please don't forget to deduplicate your installed version of @urql/core
after you upgrade.
setState
) may recursively schedule a mount, which then disabled other setState
updates from being processed. Previously we assumed that React used a trampoline scheduler for updates, however it appears that setState
can recursively start more React work, by @kitten (See #2556)Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
@urql/introspection
more specific than they need to be, this because we aren't optimizing for bundle size and in pure node usage this can confuse Node as import x from 'graphql'
won't share the same module scope as import x from 'graphql/x/y.mjs'
, by @JoviDeCroock (See #2529)Published by urql-ci over 2 years ago
subscriptionStore
and queryStore
eagerly terminating the subscription due to derived
, by @JoviDeCroock (See #2514)Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
@urql/core
in urql
package and CommonJS output for all other CommonJS-first packages. This ensures that Node.js' cjs-module-lexer
can correctly identify re-exports and report them properly. Otherwise, this will lead to a runtime error, by @kitten (See #2485)Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
Accept
header to GraphQL HTTP requests. This complies to the specification but doesn't go as far as sending Content-Type
which would throw a lot of APIs off. Instead, we'll now be sending an accept header for application/graphql+json, application/json
to indicate that we comply with the GraphQL over HTTP protocol.Accept
and Content-Type
regardless of the user options' casing, by @kitten (See #2457)withPromise
cases, by @JoviDeCroock (See #2446)text/*
as error messages, by @kitten (See #2456)Published by urql-ci over 2 years ago
isFragmentHeuristicallyMatching()
to always return true
for writes, so that we give every fragment a chance to be applied and to write to the cache, by @kitten (See #2455)clear()
was called on it, by @JoviDeCroock (See #2458)Published by urql-ci over 2 years ago
Published by urql-ci over 2 years ago
hasNext: true
queries) by shifting their layers in Graphcache behind those that are still awaiting a result. This causes continuous updates to not overwrite one-off query results while still keeping continuously updating operations at the highest possible layer, by @kitten (See #2419)relayPagination
resolver, by @tgriesser (See #2431)Published by urql-ci over 2 years ago
await executeQuery
, by @JoviDeCroock (See #2410)