You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For graphql@4 or graphql@5, we should maintain a deprecated legacy support for UMD, but switch our documentation, examples, and primary bundle to use es6 modules natively in the browser
two options:
we decide to "progressively enhance" and bundle graphiql.min.js and graphiql.js as es6 compatible modules, and add graphiql.umd(.min).js bundles for those who still need UMD
the more cautious approach would be the opposite of the above - continue publishing the canonical bundles with UMD, and add a graphiql.esm.min.js
The text was updated successfully, but these errors were encountered:
es6-module support is now available in safari and most of the browsers our potential users would be using
https://caniuse.com/es6-module
For graphql@4 or graphql@5, we should maintain a deprecated legacy support for UMD, but switch our documentation, examples, and primary bundle to use es6 modules natively in the browser
two options:
graphiql.min.js
andgraphiql.js
as es6 compatible modules, and addgraphiql.umd(.min).js
bundles for those who still need UMDgraphiql.esm.min.js
The text was updated successfully, but these errors were encountered: