Bump fast-json-patch and colyseus in /server

[dependabot]

Removes fast-json-patch. It's no longer used after updating ancestor dependency colyseus. These dependencies need to be updated together.

Removes fast-json-patch

Updates colyseus from 0.11.26 to 0.14.24

Release notes

Sourced from colyseus's releases.

0.14.18

Migrating guide to 0.14.18 https://docs.colyseus.io/migrating/0.14.18/

Breaking changes:

• The MongooseDriver should now be imported from @colyseus/mongoose-driver
• That's it! If you happen to face any issues please let us know! 🙏

This is a maintenance update - now the colyseus package has been broken down into isolated modules to avoid tying specific modules too hard with the framework. Examples of this are the new RedisDriver (thanks @​vitalyrotari) and the new uWebSocketsTransport transport option!

Here's the list of current packages in the colyseus/colyseus repository now:

• colyseus - aggregates previously existing features through their respective modules
  • @colyseus/core - all framework abstractions and features
  • @colyseus/ws-transport - default WebSocket transport (through ws module)
  • @colyseus/redis-presence - provides RedisPresence
  • @colyseus/mongoose-driver - provides MongooseDriver
• @colyseus/uwebsockets-transport - New transport option!, uses uWebSockets.js instead of ws 🥳
• @colyseus/redis-driver - colyseus/colyseus#412, thanks @​vitalyrotari!
• @colyseus/monitor - moved from its own repository into this one
• @colyseus/arena - moved from its own repository into this one

0.14.0

Check out the migration guide from 0.13 to 0.14 here.

The @​colyseus/schema has received a major restructuring internally, here's what has changed at a glance:

• Instance-sharing is now supported! You may use the same reference of a schema instance multiple times for synchronization without having to .clone() it.
• Better @filter() implementation, and the addition of @filterChildren(). Although filters are still not recommended for fast-paced games, it should serve turn-based scenarios pretty well!
• The MapSchema now uses a real Map underneath instead of plain objects.
• It is not recommended to implement constructor() inside your schemas. Use .assign({ ... }) instead.

Besides the schema changes, here are some small changes in the framework itself:

• simulateLatency(): this utility has been included to help you simulate networking delays during development.
• broadcastPatch(): this internal method has been exposed, so if you wanna have control over when to send state patches to connected clients, now you can!
• Bugfix: messages from "disconnecting" clients are now being dropped. (During some disconnection scenarios, the "client" instance of a particular "sessionId" was already removed from the server, but messages from that "sessionId" were still arriving at the server.)

The website was re-branded to focus on the maintenance and development of the framework, as well as giving more exposure to the Discord community!

Thank you all for the support! ❤

0.13.0

See how to migrate from 0.12 to 0.13

Breaking changes

• onMessage now has a required "type" argument. (#315)
• Matchmaking errors now are exposed with code and message in the client-side (317)

Reworked how to send and receive messages:

On previous versions, there was no concept of a "message type". All messages were just data being sent back and forth. Although this was simple to understand, the disadvantage is that you'd need to parse these messages and perform certain actions depending on its contents on your own.

... (truncated)

Commits

• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.