chore(deps): bump the colyseus group with 2 updates

[dependabot]

Bumps the colyseus group with 2 updates: @colyseus/sdk and @colyseus/schema.

Updates @colyseus/sdk from 0.17.34 to 0.17.42

Release notes

Sourced from @​colyseus/sdk's releases.

@​colyseus/sdk v0.17.42

• Fix H3Transport frame reassembly: a single WebTransport reader.read() is not guaranteed to land on a frame boundary, so chunks ending mid-payload or mid-varint-prefix caused sporadic handshake failures and ROOM_STATE_PATCH decode errors on rooms with larger initial state. The reader now buffers partial data across reads and only dispatches complete length-prefixed frames. Closes #934 — thanks @​anaibol for reporting and contributing the initial fix!

@​colyseus/sdk v0.17.41

• Isolate debug.js panel inside a Shadow DOM root so page-level CSS (e.g. a global canvas { width: 100vw } rule) can no longer stretch or restyle the debug UI.

@​colyseus/sdk v0.17.40

• Fix client.http.* type inference wrongly requiring query and params on endpoints that declared neither (most visible under strictNullChecks: false). Closes #933 - thanks @​thedomeffm for reporting!

@​colyseus/sdk v0.17.39

• Allow swapping the fetch implementation via fetchFn option in ClientOptions. Automatically falls back to XMLHttpRequest when fetch is unavailable (e.g. Cocos Creator Native). Closes #931 - thanks @​liangpei-web for reporting!

@​colyseus/sdk v0.17.38

• Fix HTTP response content-type detection using indexOf() instead of includes(), which caused non-JSON responses to be incorrectly parsed as JSON

@​colyseus/sdk v0.17.37

• Fix debug.js "refId not found" schema decoder errors when connection closes while latency simulation is enabled. The onclose handler is now delayed to fire after all pending onmessage callbacks.

@​colyseus/sdk v0.17.36

• Fix debug.js panel ID collision when the same sessionId is reused across rooms (e.g. QueueRoom handoff).

@​colyseus/sdk v0.17.35

• Add room.reconnection.enabled flag.
• @colyseus/sdk/debug: Use sessionStorage instead of localStorage to determine if "debug" panel is hidden.

Commits

• 3a62b72 fix(h3): reassemble frames across reads on SDK and server
• 1886a36 sdk: H3Transport reassemble frames across reads
• eb1c570 docs(changelog): credit @​asteinheiser for vite express interop report
• a7149cc fix(vite): express interop, middlewareMode support, async express callback
• f856002 fix(sdk): isolate debug.js panel in Shadow DOM
• e9fd0bb fix(traefik): support IPv6 internalAddress
• 84371c2 fix(sdk): correct client.http.* type inference when query/params undeclared
• ea6aa78 fix changelog
• 84a03f7 feat(vite): first-class Vite plugin with HMR and production builds
• 448ad06 bad claude
• Additional commits viewable in compare view

Updates @colyseus/schema from 4.0.21 to 4.0.25

Release notes

Sourced from @​colyseus/schema's releases.

4.0.25

@view(N) collections: items pushed after view.add are now visible

Items added to a non-default-tag collection (e.g. @view(1) @type([Item]) items) after the client called view.add(state, 1) were silently invisible — the array's ADD op was emitted but the new item's fields didn't share visibility with the parent.

Children of @view(N) collections now inherit parent visibility. Default-tag @view() collections keep per-item gating unchanged — view.add(item) is still required to opt each one in.

Thanks to @​FTWinston for the report and fix (#226).

4.0.24

ChangeTree.delete: fix encodeAll dropping sibling fields after undefined assignment to a @view() field

Thanks to @​Gabixel for the follow-up report after 4.0.22.

On a Schema with both @view() and non-@view() fields, assigning undefined to the @view() field evicted an unrelated sibling from allChanges. Incremental clients were fine; a fresh client joining via encodeAll() saw the sibling field silently missing.

delete() was picking its target changeset by filteredChanges !== undefined instead of mirroring change()'s per-field isFiltered test, so the matching deleteOperationAtIndex ran on the wrong side and its "find last operation" fallback removed a neighbor. Now symmetric with change() across both the *Changes and *allChanges pairs.

4.0.23

Callbacks: accept Schema instances across multiple @colyseus/schema copies

The nested-instance overloads of onAdd, onChange, onRemove, and bindTo previously declared <TInstance extends Schema, ...>. When two copies of @colyseus/schema end up in node_modules (e.g. one in the consuming app and one transitively pulled in by an SDK), TypeScript infers data parameters with a structural shape that doesn't extend the local Schema class, and TInstance collapses to the base Schema. That made CollectionPropNames<TInstance> evaluate to never, surfacing as the infamous "Argument of type '"playingUsers"' is not assignable to parameter of type 'never'" on otherwise-correct code like:

callbacks.listen("gameData", (data) => {
</tr></table> 

... (truncated)

Changelog

Sourced from @​colyseus/schema's changelog.

4.0.25

@view(N) collections: items pushed after view.add are now visible

Items added to a non-default-tag collection (e.g. @view(1) @type([Item]) items) after the client called view.add(state, 1) were silently invisible — the array's ADD op was emitted but the new item's fields didn't share visibility with the parent.

Children of @view(N) collections now inherit parent visibility. Default-tag @view() collections keep per-item gating unchanged — view.add(item) is still required to opt each one in.

Thanks to @​FTWinston for the report and fix (#226).

4.0.24

ChangeTree.delete: fix encodeAll dropping sibling fields after undefined assignment to a @view() field

Thanks to @​Gabixel for the follow-up report after 4.0.22.

On a Schema with both @view() and non-@view() fields, assigning undefined to the @view() field evicted an unrelated sibling from allChanges. Incremental clients were fine; a fresh client joining via encodeAll() saw the sibling field silently missing.

delete() was picking its target changeset by filteredChanges !== undefined instead of mirroring change()'s per-field isFiltered test, so the matching deleteOperationAtIndex ran on the wrong side and its "find last operation" fallback removed a neighbor. Now symmetric with change() across both the *Changes and *allChanges pairs.

4.0.23

Callbacks: accept Schema instances across multiple @colyseus/schema copies

The nested-instance overloads of onAdd, onChange, onRemove, and bindTo previously declared <TInstance extends Schema, ...>. When two copies of @colyseus/schema end up in node_modules (e.g. one in the consuming app and one transitively pulled in by an SDK), TypeScript infers data parameters with a structural shape that doesn't extend the local Schema class, and TInstance collapses to the base Schema. That made CollectionPropNames<TInstance> evaluate to never, surfacing as the infamous "Argument of type '"playingUsers"' is not assignable to parameter of type 'never'" on otherwise-correct code like:

</tr></table> 

... (truncated)

Commits

• 5482856 bump 4.0.25 + changelog
• 00fb219 Merge branch 'FTWinston/master'
• 82b6722 Fix issue modifying collections with non-default view tag
• a05e2e3 ChangeTree.delete: fix encodeAll dropping sibling fields after undefined as...
• 422f83a Callbacks: accept Schema instances across multiple @​colyseus/schema copies
• 8ecb9c7 bump 4.0.22 + changelog
• 091f314 StateView: fix "refId not found" when view.changes Map order is not topological
• See full diff in compare view

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]

Labels

The following labels could not be found: automated. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.