- Mark
@urql/core
as a peer dependency as well as a regular dependency Submitted by @kitten (See #3579)
- Goodbye IE11! 👋 This major release removes support for IE11. All code that is shipped will be transpiled much less and will not be ES5-compatible anymore, by @kitten (See #2504)
- Avoid making the imports of
@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 asimport x from 'graphql'
won't share the same module scope asimport x from 'graphql/x/y.mjs'
, by @JoviDeCroock (See #2529)
⚠️ Fix import ofexecuteSync
rather thanexecute
causing an incompatibility when several.mjs
imports and a mainimport { executeSync } from 'graphql'
are causing two different modules to be instantiated, by @kitten (See #2251)
- Extend peer dependency range of
graphql
to include^16.0.0
. As always when upgrading across many packages ofurql
, especially including@urql/core
we recommend you to deduplicate dependencies after upgrading, usingnpm dedupe
ornpx yarn-deduplicate
, by @kitten (See #2133)
- Add options to
@urql/introspection
'sminifyIntrospectionQuery
allowing the inclusion of more information into the minified schema as needed, namelyincludeScalars
,includeEnums
,includeInputs
, andincludeDirectives
, by @kitten (See #1578)
- Remove closure-compiler from the build step (See #1570)
- Update
minifyIntrospectionQuery
utility to remove additional information on arguments and to filter out schema metadata types, like__Field
and others, by @kitten (See #1351)
⚠️ Fix thegraphql
dependency being postfixed with.mjs
when building the package, by @JoviDeCroock (See #1204)
- Add missing
.mjs
extension to all imports fromgraphql
to fix Webpack 5 builds, which require extension-specific import paths for ESM bundles and packages. This change allows you to safely upgrade to Webpack 5., by @kitten (See #1094)
Initial Release