v4.3.18

This release aids compatibility with iOS (both the styling of the inspector and the tinybase.org website)

v4.3.17

This upgrades PartyKit dependencies and reduces E2E parallelization to reduce flakiness.

v4.3.15

This fixes a rare and pernicious bug where stopping a Persister's autoLoad twice, quickly, could remove another hook's listener.

v4.3.14

This release adds a convenient accessor to each Persister object so that you can get back a reference to the underlying storage (or name). For example, the Sqlite-based persisters all have a getDb() method to retrieve the underlying database connection, the PartyKit persister has a getConnection() method, and so on.

v4.3.13

This release lets you inspect the previous value of a Cell or Value on the PartyKit server before deciding whether to let it be updated by a client. It also slightly refactors the PartyKit server storage layer but with no breaking changes.

v4.3.12

This release adds sanitization methods to the TinyBasePartyKitServer class so that you can ensure only valid operations are being sent by a client.

For example, you can implement the canSetCell method to check that a user is allowed to change a given Cell in the durable copy of the Store on the server.

Remember that, in the general case, you cannot trust the client to only send data that the server considers valid or safe.

v4.3.11

This release adds an optional showType prop to the EditableCellView and EditableValueView components.

You can set this to false to remove the button that lets users see and change the type of the Cell or Value, which is easier than having to do it in CSS.

v4.3.10

This fixes the PartyKit peer dependency

v4.3.9

This release provides some configuration for both the server and client components of the PartyKit Persister. You can configure the store path, the durable store prefix, HTTP headers, and so on.

See the new documentation for both the client configuration and server configuration.

v4.3.8

You can now create new queries within the listeners of existing ones, which unlocks some powerful chained query functionality. Thanks @tobiascornille for the inspiration!