Skip to content

chore(deps-dev): bump the graphiql group with 4 updates - #8468

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/graphiql-f0b9530b08
Open

chore(deps-dev): bump the graphiql group with 4 updates#8468
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/graphiql-f0b9530b08

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 11, 2026

Copy link
Copy Markdown
Contributor

Bumps the graphiql group with 4 updates: @graphiql/plugin-explorer, @graphiql/react, @graphiql/toolkit and graphiql.

Updates @graphiql/plugin-explorer from 4.0.0-alpha.2 to 5.1.5

Release notes

Sourced from @​graphiql/plugin-explorer's releases.

@​graphiql/plugin-explorer@​5.1.5

Patch Changes

@​graphiql/plugin-explorer@​5.1.4

Patch Changes

@​graphiql/plugin-explorer@​5.1.3

Patch Changes

@​graphiql/plugin-explorer@​5.1.3-alpha.0

Patch Changes

  • Updated dependencies [5f44a27]:
    • @​graphiql/react@​0.37.6-alpha.0

@​graphiql/plugin-explorer@​5.1.2

Patch Changes

@​graphiql/plugin-explorer@​5.1.1

Patch Changes

Changelog

Sourced from @​graphiql/plugin-explorer's changelog.

5.1.5

Patch Changes

5.1.4

Patch Changes

5.1.3

Patch Changes

5.1.2

Patch Changes

5.1.1

Patch Changes

5.1.0

Minor Changes

Patch Changes

5.0.0

Major Changes

  • #3990 27e7eb6 Thanks @​dimaMachina! - - allow multiple independent instances of GraphiQL on the same page
    • store onClickReference in query editor in React ref

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​graphiql/plugin-explorer since your current version.


Updates @graphiql/react from 1.0.0-alpha.4 to 1.0.0-next.2

Release notes

Sourced from @​graphiql/react's releases.

@​graphiql/react@​1.0.0-beta.1

Patch Changes

  • #4471 cb2ac2a Thanks @​trevor-scheer! - Pin internal @graphiql/react and @graphiql/toolkit dependency ranges to exact beta versions, so caret prerelease ranges can no longer resolve to the 1.0.0-next.* builds published in 2022.

@​graphiql/react@​1.0.0-beta.0

Major Changes

  • #4423 f45e26b Thanks @​trevor-scheer! - cn is no longer exported from @graphiql/react; import clsx directly.

  • #4393 827da62 Thanks @​trevor-scheer! - Remove deprecated hooks: useEditorContext, useExecutionContext, usePluginContext, useSchemaContext, useTheme, useStorage, useStorageContext, usePrettifyEditors, useCopyQuery, useMergeQuery, the *Store aliases (in @graphiql/react); useExplorerContext (in @graphiql/plugin-doc-explorer); and useHistoryContext (in @graphiql/plugin-history). Replacements were available since v5 — see the v6 migration guide for one-line replacements.

Minor Changes

  • #4359 ac56840 Thanks @​trevor-scheer! - New @graphiql/plugin-collections plugin for saving named operations into folder collections and reusing them later, default-installed in the graphiql meta-package so a Collections rail icon appears out of the box (passing the plugins prop opts out of the default set as before).

    • Collapsible tree UI with inline rename, hover-revealed row actions, and QRY/MUT/SUB pills (a MIX pill when a saved document holds more than one operation).
    • Save the current operation with ⌘S/Ctrl+S or the tab-strip Save button. An operation opened from a collection stays linked, so re-saving updates it in place; otherwise a "Save to collection" dialog opens. Clicking a saved item opens it in a new tab.
    • Reorder within and across collections by drag-and-drop or keyboard (focus a row's drag handle, Space to grab, arrow keys to move, Space to drop, Escape to cancel).
    • Copy a raw query or Share an importable envelope from any row; collection headers expose Share. Paste or drop a collections export anywhere in the pane to merge it in, or import/export JSON from the dialog. Imports reconcile by stable id, so re-importing updates in place and never duplicates; a conflict dialog lets you apply incoming changes, keep yours, or review each, and merge never deletes.
    • Pluggable persistence via the storage option (defaults to localStorage), plus readOnly, allowImportExport, and allowReplace for governed deployments.

    To support this without the core depending on any specific plugin, @graphiql/react gains a save API: registerSaveHandler(handler) (⌘S and the Save button fan out to every registered handler plus the onSaveQuery prop, and the dirty-state affordance only appears when at least one is registered), the onSaveQuery(tab) prop with markTabSaved(tabId) for deferred saves, and GraphiQLPlugin.sessionActions, an always-mounted plugin slot for toolbar buttons, dialogs, or behavior registration. The dirty-state dot means "a saved operation has unsaved edits" and survives a reload, so a tab that was never saved reads clean.

  • #4277 d4f0268 Thanks @​trevor-scheer! - Add a KeycapHint primitive for displaying inline keyboard shortcuts (e.g. ⌘K, ⌘⏎), available for general consumer use. It takes semantic modifier names via the MODIFIER constant: MODIFIER.Meta renders as ⌘ on macOS and Ctrl elsewhere; Ctrl/Alt/Shift render as Mac glyphs (⌃/⌥/⇧) on macOS and plain text on other platforms; Enter renders as ⏎ everywhere.

  • #4285 c25bfd5 Thanks @​trevor-scheer! - Add a MethodPill primitive: a small colored pill labeling an operation as QRY (query), MUT (mutation), or SUB (subscription).

  • #4352 f8a9445 Thanks @​trevor-scheer! - The active operation now follows the editor cursor. As you move the cursor between operations in a multi-operation document, operationName updates to the operation the cursor sits in, so the operation dropdown and operation-aware plugins all reflect where you are editing. Previously operationName only changed on run-at-cursor or via the operation dropdown.

    Two consequences if you embed GraphiQL: the onEditOperationName callback now fires when the cursor crosses into a different named operation, and a tab containing multiple operations shows the active operation name with a +N count of the others. Pinning an operation with the operationName prop still overrides cursor tracking.

    The Run button now offers an operation picker: in a document with multiple named operations, a dropdown on the Run button lets you choose which operation to run, and the menu marks which operation is currently active. The active operation still follows the editor cursor by default.

  • #4284 1ce71e4 Thanks @​trevor-scheer! - Add a PanelHeader primitive for side panels. Renders a title, optional subtitle, and optional action-icon row.

  • #4321 03535ab Thanks @​trevor-scheer! - Add a response pane header with real status, elapsed time, and response size from the active transport, a copy button, and a JSON / Tree / Table view toggle (the selection is persisted and restored on reload).

    • Tree renders the response JSON as a collapsible tree with type-colored values; top-level nodes expand by default and deeper levels start collapsed.
    • Table renders each list field as its own table captioned with its path (e.g. test.person.friends); sibling and aliased lists each get a table, nested objects and arrays show as shorthand summaries, non-list responses show an empty state, and rows get a bottom divider.

  • #4282 a0fe11a Thanks @​trevor-scheer! - Add a SegmentedControl primitive for selecting one option from a small set inline, used by the response view toggle and several settings controls. It is built on native radio inputs, so keyboard navigation (arrow keys, Home / End) and screen-reader semantics come from the browser and the group is a single tab stop.

  • #4338 480afc1 Thanks @​trevor-scheer! - Add a SettingsDialog with theme, density, font-size, and persist-headers controls, backed by a new useGraphiQLSettings() hook that persists preferences to localStorage and applies them to the GraphiQL container via data-* attributes. Density and font-size presets fill in concrete token values for the [data-density] and [data-font-size] blocks in tokens.css; Monaco editor font size, the status bar, and UI icon sizes follow the active font-size preset. The forcedTheme and showPersistHeadersSettings props continue to work, with forcedTheme hiding the theme control.

  • #4333 093cb10 Thanks @​trevor-scheer! - Add a structured Transport API alongside the existing Fetcher. createTransport({...}) performs the GraphQL request and returns a TransportResponse carrying the real HTTP wire metadata (status, headers, timing, size) for queries, mutations, subscriptions, and incremental delivery, so the response pane can surface those values directly instead of fabricating them. That metadata is there even when the response body isn't valid JSON (an HTML error page from a proxy, a plain-text 401), so a broken response still shows its real status code instead of a generic error. <GraphiQL> accepts a new transport prop, mutually exclusive with fetcher at the type level.

    Transports support GET, POST, and the HTTP QUERY method per the GraphQL over HTTP spec. Pass method / supportedMethods to choose; GET encodes the query into the URL with no body, QUERY sends a JSON body but is safe and idempotent, and mutations are always sent over POST (or blocked when POST is unavailable). Transport exposes url, method, supportedMethods, and an optional setMethod, and the top bar shows the active method and endpoint with an inline switcher that cycles through the supported methods. Every request, incremental delivery on or off, sends application/graphql-response+json in its accept header alongside application/json, so spec-compliant servers don't fall back to legacy response semantics. Subscriptions require an explicit subscriptionClient satisfying a small SubscriptionClient contract: a single .subscribe(request, sink) method that graphql-ws and graphql-sse clients meet directly. The low-level simpleHttpTransport and multipartHttpTransport primitives also accept an optional method.

    TransportRequest carries extensions for GraphQL-over-HTTP extensions such as automatic persisted queries (encoded into the URL for GET, included in the JSON body for POST and QUERY), and signal, an AbortSignal that cancels an in-flight query or mutation. Stopping a running query or mutation aborts the request; stopping a subscription closes the underlying socket or SSE connection. TransportResponse.ok reflects both layers: the HTTP status and the absence of top-level GraphQL errors, so a 401 or 500 is never ok: true just because its body happens to parse as JSON with no errors.

    Plugins can observe and transform traffic through transport.onBeforeSend, transport.onResponse, and transport.onError, available via useGraphiQLPluginContext() (all three return a cleanup function; the transport field is undefined under the legacy fetcher path, so guard with optional chaining). onError fires when a request fails outright, such as a network error, so plugins can react to failures the same way they observe successful responses.

... (truncated)

Changelog

Sourced from @​graphiql/react's changelog.

@​graphiql/react

0.39.0

Minor Changes

  • #4462 1cb7eba Thanks @​JoviDeCroock! - Add opt-in GraphQL 17 fragment argument syntax support to parsing, validation, type information, autocomplete, hover, and editor integrations. Enable it with experimentalFragmentArguments: true; it defaults to false until server capabilities can advertise support.

    Also fix variable autocomplete to respect operation and fragment scope while including variables from operations that spread the current fragment.

Patch Changes

  • #4468 65867b5 Thanks @​therealyo! - Keep the active tab selected when a tab to its right is closed. closeTab decremented activeTabIndex unconditionally, without comparing it to the index of the closed tab. Closing a tab positioned after the active one does not shift the active tab Closing the active tab, or a tab before it, is unchanged.

  • #4476 6d57aad Thanks @​trevor-scheer! - Fix an extra empty tab being created on reload. The query/variables/headers storage keys are only written on edit, so reloading a session that never touched the editors found no stored editor state matching any tab and pushed a new empty one.

  • Updated dependencies [d0a34f4, 1cb7eba, 296214d]:

0.38.0

Minor Changes

  • #4448 e751f65 Thanks @​dargmuesli! - Add customScalarSchemas prop to GraphiQLProvider/GraphiQL, forwarded to monaco-graphql's per-schema customScalarSchemas config. Without it, the variable editor's live JSON Schema linter assumes every custom scalar only accepts primitives (string, number, boolean, integer) and reports a spurious "Incorrect type" error for scalars that legitimately accept objects or arrays (e.g. a JSON or GeoJSON scalar). graphql-language-service and monaco-graphql already supported this per-scalar override; @graphiql/react just never exposed it.

Patch Changes

  • #4430 6090495 Thanks @​trevor-scheer! - Disable Fira Code's font ligatures in the Monaco editors. Programming ligatures rewrote valid GraphQL into misleading glyphs — most notably Int!=1 (a non-null Int with a default value of 1) rendered as Int≠1, implying an inequality that isn't there. Characters now render literally. The Windows caret fix from #4040 is preserved.

  • Updated dependencies [0893da7]:

0.37.7

Patch Changes

0.37.6

... (truncated)

Commits

Updates @graphiql/toolkit from 0.9.1 to 0.12.1

Release notes

Sourced from @​graphiql/toolkit's releases.

@​graphiql/toolkit@​0.12.1

Patch Changes

@​graphiql/toolkit@​0.12.0

Minor Changes

Changelog

Sourced from @​graphiql/toolkit's changelog.

0.12.1

Patch Changes

0.12.0

Minor Changes

0.11.3

Patch Changes

0.11.2

Patch Changes

0.11.1

Patch Changes

0.11.0

Minor Changes

0.10.0

Minor Changes

0.9.2

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​graphiql/toolkit since your current version.


Updates graphiql from 4.0.0-alpha.5 to 5.4.0

Release notes

Sourced from graphiql's releases.

[email protected]

Minor Changes

  • #4462 1cb7eba Thanks @​JoviDeCroock! - Add opt-in GraphQL 17 fragment argument syntax support to parsing, validation, type information, autocomplete, hover, and editor integrations. Enable it with experimentalFragmentArguments: true; it defaults to false until server capabilities can advertise support.

    Also fix variable autocomplete to respect operation and fragment scope while including variables from operations that spread the current fragment.

Patch Changes

[email protected]

Minor Changes

  • #4448 e751f65 Thanks @​dargmuesli! - Add customScalarSchemas prop to GraphiQLProvider/GraphiQL, forwarded to monaco-graphql's per-schema customScalarSchemas config. Without it, the variable editor's live JSON Schema linter assumes every custom scalar only accepts primitives (string, number, boolean, integer) and reports a spurious "Incorrect type" error for scalars that legitimately accept objects or arrays (e.g. a JSON or GeoJSON scalar). graphql-language-service and monaco-graphql already supported this per-scalar override; @graphiql/react just never exposed it.

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

  • Updated dependencies [5f44a27]:
    • @​graphiql/react@​0.37.6-alpha.0
    • @​graphiql/plugin-doc-explorer@​0.4.3-alpha.0
    • @​graphiql/plugin-history@​0.4.3-alpha.0

[email protected]

Patch Changes

... (truncated)

Changelog

Sourced from graphiql's changelog.

5.4.0

Minor Changes

  • #4462 1cb7eba Thanks @​JoviDeCroock! - Add opt-in GraphQL 17 fragment argument syntax support to parsing, validation, type information, autocomplete, hover, and editor integrations. Enable it with experimentalFragmentArguments: true; it defaults to false until server capabilities can advertise support.

    Also fix variable autocomplete to respect operation and fragment scope while including variables from operations that spread the current fragment.

Patch Changes

5.3.0

Minor Changes

  • #4448 e751f65 Thanks @​dargmuesli! - Add customScalarSchemas prop to GraphiQLProvider/GraphiQL, forwarded to monaco-graphql's per-schema customScalarSchemas config. Without it, the variable editor's live JSON Schema linter assumes every custom scalar only accepts primitives (string, number, boolean, integer) and reports a spurious "Incorrect type" error for scalars that legitimately accept objects or arrays (e.g. a JSON or GeoJSON scalar). graphql-language-service and monaco-graphql already supported this per-scalar override; @graphiql/react just never exposed it.

Patch Changes

5.2.4

Patch Changes

5.2.3

Patch Changes

  • #4181 f1a210e Thanks @​trevor-scheer! - Fix schema prop to skip introspection when IntrospectionQuery data is provided

    Previously, passing an IntrospectionQuery result as the schema prop would still trigger a network introspection request. The shouldIntrospect check only recognized GraphQLSchema instances (via isSchema), not raw introspection data. Now, when an IntrospectionQuery is passed, a schema is built from it directly using buildClientSchema and introspection is skipped.

  • #4211 e7b30c1 Thanks @​davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for graphiql since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps-dev): bump the graphiql group with 4 updates
3da341a 
Bumps the graphiql group with 4 updates: [@graphiql/plugin-explorer](https://github.com/graphql/graphiql/tree/HEAD/packages/graphiql-plugin-explorer), [@graphiql/react](https://github.com/graphql/graphiql/tree/HEAD/packages/graphiql-react), [@graphiql/toolkit](https://github.com/graphql/graphiql/tree/HEAD/packages/graphiql-toolkit) and [graphiql](https://github.com/graphql/graphiql/tree/HEAD/packages/graphiql).


Updates `@graphiql/plugin-explorer` from 4.0.0-alpha.2 to 5.1.5
- [Release notes](https://github.com/graphql/graphiql/releases)
- [Changelog](https://github.com/graphql/graphiql/blob/main/packages/graphiql-plugin-explorer/CHANGELOG.md)
- [Commits](https://github.com/graphql/graphiql/commits/@graphiql/[email protected]/packages/graphiql-plugin-explorer)

Updates `@graphiql/react` from 1.0.0-alpha.4 to 1.0.0-next.2
- [Release notes](https://github.com/graphql/graphiql/releases)
- [Changelog](https://github.com/graphql/graphiql/blob/main/packages/graphiql-react/CHANGELOG.md)
- [Commits](https://github.com/graphql/graphiql/commits/HEAD/packages/graphiql-react)

Updates `@graphiql/toolkit` from 0.9.1 to 0.12.1
- [Release notes](https://github.com/graphql/graphiql/releases)
- [Changelog](https://github.com/graphql/graphiql/blob/main/packages/graphiql-toolkit/CHANGELOG.md)
- [Commits](https://github.com/graphql/graphiql/commits/@graphiql/[email protected]/packages/graphiql-toolkit)

Updates `graphiql` from 4.0.0-alpha.5 to 5.4.0
- [Release notes](https://github.com/graphql/graphiql/releases)
- [Changelog](https://github.com/graphql/graphiql/blob/main/packages/graphiql/CHANGELOG.md)
- [Commits](https://github.com/graphql/graphiql/commits/[email protected]/packages/graphiql)

---
updated-dependencies:
- dependency-name: "@graphiql/plugin-explorer"
  dependency-version: 5.1.5
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: graphiql
- dependency-name: "@graphiql/react"
  dependency-version: 1.0.0-next.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: graphiql
- dependency-name: "@graphiql/toolkit"
  dependency-version: 0.12.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: graphiql
- dependency-name: graphiql
  dependency-version: 5.4.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: graphiql
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies javascript Pull requests that update javascript code labels Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies javascript Pull requests that update javascript code

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants