unstale

npm / @graphql-yoga/plugin-graphql-sse

@graphql-yoga/plugin-graphql-sse

What changed in @graphql-yoga/plugin-graphql-sse 3 to 4, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-12.

14 breaking1 behavior and defaults

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

npx @unstale/cli init

@unstale/cli 0.2.12 on npm

@graphql-yoga/plugin-graphql-sse 48 changes

Breaking changes 7

  • Plugins added with addPlugin are inserted inplace, so their hooks execute immediately after the plugin that added them rather than last.

    4.0.0upgrade guide

  • Install the new NPM package with npm i graphql-yoga.

    4.0.0upgrade guide

  • Request bodies are now limited to 25,000,000 bytes by default; set maxRequestBodySize: false in createYoga to disable the limit.

    4.0.0release notes

  • GraphQL 16 is now the minimum supported version; GraphQL 14 and 15 are no longer supported.

    4.0.0release notes

  • Node 22 is now the minimum supported version; Node 18 and 20 are no longer supported.

    4.0.0release notes

  • Node.js v16 is no longer supported.

    3.0.0, 4.0.0upgrade guiderelease notes

  • POST body parsing is asynchronous due to the body-size limit, so yoga.fetch() can return a Promise instead of a synchronous Response; await it and response body parsing.

    4.0.0release notes

Behavior and default changes 1

  • SSE operations now use the same request pipeline as HTTP, so onParams-based plugins are enforced consistently across both transports.

    4.1.0release notes

@graphql-yoga/plugin-graphql-sse 37 changes

Breaking changes 7

  • This unused graphiql option was removed completely.

    3.0.0upgrade guide

  • Subscriptions now use GraphQL over SSE “distinct connections mode” instead of Yoga’s custom SSE transport; clients are recommended to use graphql-sse.

    3.0.0upgrade guide

  • This unused graphiql option was removed completely.

    3.0.0upgrade guide

  • Subscriptions no longer support multipart/mixed and use text/event-stream as the transport method.

    3.0.0upgrade guide

  • Parsing and validation caches are configured together under this option, including documentCache, errorCache, and validationCache.

    3.0.0upgrade guide

  • The separate parser cache option is replaced by parserAndValidationCache.

    3.0.0upgrade guide

  • The separate validation cache option is replaced by parserAndValidationCache.

    3.0.0upgrade guide