fix(deps): update minor and patch dependencies for gatsby

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-codegen/typescript	^2.8.7 -> ^2.8.8
@graphql-codegen/typescript-operations	^2.5.12 -> ^2.5.13
@graphql-tools/code-file-loader	^7.3.16 -> ^7.3.23
@graphql-tools/load	^7.8.10 -> ^7.8.14
@jridgewell/trace-mapping	^0.3.17 -> ^0.3.18
@types/http-proxy (source)	^1.17.9 -> ^1.17.11
autoprefixer	^10.4.13 -> ^10.4.14
browserslist	^4.21.4 -> ^4.21.5
date-fns	^2.29.3 -> ^2.30.0
deepmerge	^4.3.0 -> ^4.3.1
enhanced-resolve	^5.12.0 -> ^5.13.0
graphql-http	^1.13.0 -> ^1.18.0
joi	^17.7.0 -> ^17.9.2
node-fetch	^2.6.8 -> ^2.6.9
postcss (source)	^8.4.21 -> ^8.4.23
react-server-dom-webpack	0.0.0-experimental-c8b778b7f-20220825 -> 0.0.1
slugify	^1.6.5 -> ^1.6.6
socket.io	4.5.4 -> 4.6.1
socket.io-client	4.5.4 -> 4.6.1
terser-webpack-plugin	^5.3.6 -> ^5.3.7
webpack	^5.75.0 -> ^5.81.0
xstate (source)	^4.35.3 -> ^4.37.2

---

Release Notes

ardatan/graphql-tools (@​graphql-tools/code-file-loader)

v7.3.23

Compare Source

Patch Changes

• Updated dependencies [05c97eb8]:
  • @​graphql-tools/graphql-tag-pluck@​7.5.2

v7.3.22

Compare Source

Patch Changes

• 1c95368a Thanks @​ardatan! - Use ranged versions for dependencies

• Updated dependencies [1c95368a]:

  • @​graphql-tools/graphql-tag-pluck@​7.5.1

v7.3.21

Compare Source

Patch Changes

• Updated dependencies [42ad8df8]:
  • @​graphql-tools/graphql-tag-pluck@​7.5.0

v7.3.20

Compare Source

Patch Changes

• #​5030 bb2d257b Thanks @​mscharley! - Added the ability to parse cjs/mjs files for graphql documents

• Updated dependencies [bb2d257b]:

  • @​graphql-tools/graphql-tag-pluck@​7.4.6

v7.3.19

Compare Source

Patch Changes

• Updated dependencies [b5c8f640]:
  • @​graphql-tools/utils@​9.2.1
  • @​graphql-tools/graphql-tag-pluck@​7.4.5

v7.3.18

Compare Source

Patch Changes

• Updated dependencies [a94217e9, 62d074be]:
  • @​graphql-tools/utils@​9.2.0
  • @​graphql-tools/graphql-tag-pluck@​7.4.4

ardatan/graphql-tools (@​graphql-tools/load)

v7.8.14

Compare Source

Patch Changes

• 1c95368a Thanks @​ardatan! - Use ranged versions for dependencies

• Updated dependencies [1c95368a]:

  • @​graphql-tools/schema@​9.0.18

v7.8.13

Compare Source

Patch Changes

• Updated dependencies []:
  • @​graphql-tools/schema@​9.0.17

v7.8.12

Compare Source

Patch Changes

• Updated dependencies [b5c8f640]:
  • @​graphql-tools/utils@​9.2.1
  • @​graphql-tools/schema@​9.0.16

v7.8.11

Compare Source

Patch Changes

• Updated dependencies [a94217e9, 62d074be]:
  • @​graphql-tools/utils@​9.2.0
  • @​graphql-tools/schema@​9.0.15

jridgewell/trace-mapping

v0.3.18

Compare Source

What's Changed

• fix: add "types" field to package.json by @​dominikg in https://github.com/jridgewell/trace-mapping/pull/24

New Contributors

• @​dominikg made their first contribution in https://github.com/jridgewell/trace-mapping/pull/24

Full Changelog: jridgewell/trace-mapping@v0.3.17...v0.3.18

date-fns/date-fns

v2.30.0

Compare Source

Kudos to @​kossnocorp and @​Andarist for working on the release.

Changes

• Fixed increased build size after enabling compatibility with older browsers in the previous release. This was done by adding @​babel/runtime as a dependency. See more details.

TehShrike/deepmerge

v4.3.1

Compare Source

• Fix type definition for arrayMerge options. #​239

graphql/graphql-http

v1.18.0

Compare Source

Bug Fixes

• audits/server: Avoid auditing non well-formatted GraphQL-over-HTTP requests (#​62) (d72e344)
• audits/server: Prefer using POST (#​77) (8cd7dfb)
• handler: Stringify errors by exposing only the message (cabf8a9)

Features

• audits: Notices section for optional recommendations (#​76) (b8bdc71)
• handler: Error formatter function (#​78) (c0eaeb4)

1.17.1 (2023-03-31)

Bug Fixes

• Add file extensions to imports/exports in ESM type definitions (d084a8d), closes #​70
• audits/server: Better "must accept UTF-8" test with emoji (#​69) (a322d2c)

v1.17.1

Compare Source

Bug Fixes

• Add file extensions to imports/exports in ESM type definitions (d084a8d), closes #​70
• audits/server: Better "must accept UTF-8" test with emoji (#​69) (a322d2c)

v1.17.0

Compare Source

Features

• use/express,use/fastify,use/koa: Request context with the response (665175e), closes #​66
• use/http,use/http2: Request context with the response (e2cc0cd), closes #​66

v1.16.0

Compare Source

Bug Fixes

• audits/render: Clone response to allow re-reading the body (#​55) (dd4f5f1)

Features

• use: Deprecate node adapter in favor of http and http2 adapters (f5b0305)
• use: Each adapter has an adapted HandlerOptions interface (f14a821)

v1.15.0

Compare Source

Features

• audits/render: Render audit results to HTML with renderAuditResultsToHTML (#​53) (da32059)
• Bundle the audits into UMD for browser usage (a402823)
• Server compliance audit through a website (#​54) (f23a689), closes #​8

v1.14.0

Compare Source

Features

• handler: Add validationRules option for extending or replacing the GraphQL validation rule set (#​51) (46c5309)

postcss/postcss

v8.4.23

Compare Source

• Fixed warnings in TypeDoc.

v8.4.22

Compare Source

• Fixed TypeScript support with node16 (by Remco Haszing).

facebook/react

v0.0.0-experimental-d962f35ca-20230418

Compare Source

simov/slugify

v1.6.6

Compare Source

• #​174 correctly handle empty strings in charmaps (@​iliazeus)
• #​169 Add changelog (@​simov)
• #​168 chore: document limitations of the remove option (#​168) (@​Trott)
• #​157 Run CI in Node.js 18 (@​stscoundrel)
• #​151 Update README.md (#​151) (@​lorand-horvath)

socketio/socket.io

v4.6.1

Compare Source

Bug Fixes

• properly handle manually created dynamic namespaces (0d0a7a2)
• types: fix nodenext module resolution compatibility (#​4625) (d0b22c6)

Dependencies

• engine.io@~6.4.0 (no change)
• ws@~8.11.0 (no change)

v4.6.0

Compare Source

Bug Fixes

• add timeout method to remote socket (#​4558) (0c0eb00)
• typings: properly type emits with timeout (f3ada7d)

Features

Promise-based acknowledgements

This commit adds some syntactic sugar around acknowledgements:

• emitWithAck()

try {
  const responses = await io.timeout(1000).emitWithAck("some-event");
  console.log(responses); // one response per client
} catch (e) {
  // some clients did not acknowledge the event in the given delay
}

io.on("connection", async (socket) => {
    // without timeout
  const response = await socket.emitWithAck("hello", "world");

  // with a specific timeout
  try {
    const response = await socket.timeout(1000).emitWithAck("hello", "world");
  } catch (err) {
    // the client did not acknowledge the event in the given delay
  }
});

• serverSideEmitWithAck()

try {
  const responses = await io.timeout(1000).serverSideEmitWithAck("some-event");
  console.log(responses); // one response per server (except itself)
} catch (e) {
  // some servers did not acknowledge the event in the given delay
}

Added in 184f3cf.

Connection state recovery

This feature allows a client to reconnect after a temporary disconnection and restore its state:

• id
• rooms
• data
• missed packets

Usage:

import { Server } from "socket.io";

const io = new Server({
  connectionStateRecovery: {
    // default values
    maxDisconnectionDuration: 2 * 60 * 1000,
    skipMiddlewares: true,
  },
});

io.on("connection", (socket) => {
  console.log(socket.recovered); // whether the state was recovered or not
});

Here's how it works:

• the server sends a session ID during the handshake (which is different from the current id attribute, which is public and can be freely shared)
• the server also includes an offset in each packet (added at the end of the data array, for backward compatibility)
• upon temporary disconnection, the server stores the client state for a given delay (implemented at the adapter level)
• upon reconnection, the client sends both the session ID and the last offset it has processed, and the server tries to restore the state

The in-memory adapter already supports this feature, and we will soon update the Postgres and MongoDB adapters. We will also create a new adapter based on Redis Streams, which will support this feature.

Added in 54d5ee0.

Compatibility (for real) with Express middlewares

This feature implements middlewares at the Engine.IO level, because Socket.IO middlewares are meant for namespace authorization and are not executed during a classic HTTP request/response cycle.

Syntax:

io.engine.use((req, res, next) => {
  // do something

  next();
});

// with express-session
import session from "express-session";

io.engine.use(session({
  secret: "keyboard cat",
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

// with helmet
import helmet from "helmet";

io.engine.use(helmet());

A workaround was possible by using the allowRequest option and the "headers" event, but this feels way cleaner and works with upgrade requests too.

Added in 24786e7.

Error details in the disconnecting and disconnect events

The disconnect event will now contain additional details about the disconnection reason.

io.on("connection", (socket) => {
  socket.on("disconnect", (reason, description) => {
    console.log(description);
  });
});

Added in 8aa9499.

Automatic removal of empty child namespaces

This commit adds a new option, "cleanupEmptyChildNamespaces". With this option enabled (disabled by default), when a socket disconnects from a dynamic namespace and if there are no other sockets connected to it then the namespace will be cleaned up and its adapter will be closed.

import { createServer } from "node:http";
import { Server } from "socket.io";

const httpServer = createServer();
const io = new Server(httpServer, {
  cleanupEmptyChildNamespaces: true
});

Added in 5d9220b.

A new "addTrailingSlash" option

The trailing slash which was added by default can now be disabled:

import { createServer } from "node:http";
import { Server } from "socket.io";

const httpServer = createServer();
const io = new Server(httpServer, {
  addTrailingSlash: false
});

In the example above, the clients can omit the trailing slash and use /socket.io instead of /socket.io/.

Added in d0fd474.

Performance Improvements

• precompute the WebSocket frames when broadcasting (da2b542)

Dependencies

• engine.io@~6.4.0 (socketio/engine.io@6.2.1...6.4.0)
• ws@~8.11.0 (websockets/ws@8.2.3...8.11.0)

socketio/socket.io-client

v4.6.1

Compare Source

Bug Fixes

• do not drain the queue while the socket is offline (4996f9e)
• prevent duplicate connections when multiplexing (46213a6)

Dependencies

• engine.io-client@~6.4.0 (no change)
• ws@~8.11.0 (no change)

v4.6.0

Compare Source

Bug Fixes

• typings: do not expose browser-specific types (4d6d95e)
• ensure manager.socket() returns an active socket (b7dd891)
• typings: properly type emits with timeout (#​1570) (33e4172)

Features

A new "addTrailingSlash" option

The trailing slash which was added by default can now be disabled:

import { io } from "socket.io-client";

const socket = io("https://example.com", {
  addTrailingSlash: false
});

In the example above, the request URL will be https://example.com/socket.io instead of https://example.com/socket.io/.

Added in 21a6e12.

Promise-based acknowledgements

This commit adds some syntactic sugar around acknowledgements:

// without timeout
const response = await socket.emitWithAck("hello", "world");

// with a specific timeout
try {
  const response = await socket.timeout(1000).emitWithAck("hello", "world");
} catch (err) {
  // the server did not acknowledge the event in the given delay
}

Note: environments that do not support Promises will need to add a polyfill in order to use this feature.

Added in 47b979d.

Connection state recovery

This feature allows a client to reconnect after a temporary disconnection and restore its ID and receive any packets that was missed during the disconnection gap. It must be enabled on the server side.

A new boolean attribute named recovered is added on the socket object:

socket.on("connect", () => {
  console.log(socket.recovered); // whether the recovery was successful
});

Added in 54d5ee0 (server) and b4e20c5 (client).

Retry mechanism

Two new options are available:

• retries: the maximum number of retries. Above the limit, the packet will be discarded.
• ackTimeout: the default timeout in milliseconds used when waiting for an acknowledgement (not to be mixed up with the already existing timeout option, which is used by the Manager during the connection)

const socket = io({
  retries: 3,
  ackTimeout: 10000
});

// implicit ack
socket.emit("my-event");

// explicit ack
socket.emit("my-event", (err, val) => { /* ... */ });

// custom timeout (in that case the ackTimeout is optional)
socket.timeout(5000).emit("my-event", (err, val) => { /* ... */ });

In all examples above, "my-event" will be sent up to 4 times (1 + 3), until the server sends an acknowledgement.

Assigning a unique ID to each packet is the duty of the user, in order to allow deduplication on the server side.

Added in 655dce9.

Dependencies

• engine.io-client@~6.4.0 (diff)
• ws@~8.11.0 (diff)

statelyai/xstate

v4.37.2

Compare Source

Patch Changes

• #​3972 2b9583a63 Thanks @​Andarist! - The "Some implementations missing" type-level error will now mention what implementations are missing.

---

Configuration

📅 Schedule: Branch creation - "before 7am on the first day of the month" in timezone GMT, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.