unstale

npm / @graphiql/plugin-explorer

@graphiql/plugin-explorer

What changed in @graphiql/plugin-explorer 4 to 5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-23.

5 breaking1 deprecations1 behavior and defaults1 tooling2 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.4 on npm

@graphiql/plugin-explorer 55 changes

Breaking changes 2

  • When adding a custom plugin such as Explorer, explicitly include HISTORY_PLUGIN in the plugins array to keep the History plugin.

    5.0.0upgrade guide

  • The UMD build is removed; use the ESM CDN example instead.

    5.0.0upgrade guide

Behavior and default changes 1

  • Comments are now supported in the Variables and Headers editors.

    5.0.0release notes

Tooling 1

  • GraphiQL 5 is powered by the latest version of the Monaco editor.

    5.0.0release notes

Fixes and other changes 1

  • Adds CSS files to sideEffects so CSS can be imported in Webpack JavaScript.

    5.1.2release notes

@graphiql/plugin-explorer 45 changes

Breaking changes 3

  • CommonJS build output was dropped; the package now provides ESM output.

    4.0.0upgrade guide

  • The style import path changed from @graphiql/plugin-explorer/dist/style.css to @graphiql/plugin-explorer/style.css.

    4.0.0upgrade guide

  • Support for React 16/17 was dropped, and support for React 19 was added.

    4.0.0upgrade guide

Deprecations 1

  • The UMD build is deprecated; migrate to the ESM-based CDN.

    4.0.0upgrade guide

Fixes and other changes 1