d5d0b663c9
* Bump @vitest/mocker in the npm_and_yarn group across 0 directory Updates `@vitest/mocker` from 4.1.10 to 5.0.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/mocker) --- updated-dependencies: - dependency-name: "@vitest/mocker" dependency-version: 5.0.0 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]> * [AI] Fix typecheck failures under vitest 5 Vitest 5 changed two things that broke the typecheck/build jobs: - `vi.fn()`'s inferred type now references `Procedure` from an internal vitest chunk that cannot be named from outside, so the hoisted mocks in `cloud-storage.test.ts` tripped TS2883. Annotate them as `Mock`. - The `expect` package was inlined and the global `jest.Matchers` declaration dropped, so `@testing-library/jest-dom`'s default entry no longer augments vitest's `Assertion`. Use the `/vitest` entry point instead. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Bvwt76cXUoLwfHiy1jhToc * [AI] Bump @actual-app/crdt to 3.1.3 The dependency bump touches packages/crdt/package.json, so the CRDT version bump check requires a new version. Matches how the previous dependabot group bump (#8921) was handled. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Bvwt76cXUoLwfHiy1jhToc * [AI] Add release note for the vitest bump Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Bvwt76cXUoLwfHiy1jhToc --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: MatissJanis <[email protected]> Co-authored-by: Claude Opus 5 <[email protected]>
@actual-app/crdt
This package contains the core CRDT logic that enables Actual's syncing. It is shared between the client and server. We may or may not follow semver when updating this package; any usage of it outside Actual is undocumented and at your own risk.
protobuf
We use protobuf to encode messages as binary data to send across the network.
Generating protobuf
The protobuf is generated by using the protoc compiler.
This can be installed by downloading one of the pre-built binaries and placing it in your $PATH. The version used to build the current protobuf is v3.20.1. You'll also need to download the latest version of protoc-gen-js. For convenience, you can put both of these binaries in ./bin.
Once installed, the protobuf can be generated by running ./bin/generate-proto.
However there is one very important thing to remember! The default output includes this near the top:
var global = (function() { return this || window || global || self || Function('return this')(); }).call(null);
This will not work with our CSP directives. You must manually modify this to this:
var global = globalThis;