Releases: rocicorp/replicache
Releases · rocicorp/replicache
v5.0.1
Client View URL is now required
The Replicache constructor now requires you to pass in the clientViewURL
. See Replicache Server Setup
v4.0.0
v3.1.0
v3.0.0
createIndex
anddropIndex
are only available onReplicache
class (no longer part of aWriteTransaction
).- Better handling of the
wasm
file when using Webpack (see sample/next). - Fixed issue when a mutator was missing which lead to an iloop.
- When scanning over an index, the result key is tuple of
[secondary, primary]
. Similarly when starting a scan over an index at a key you can now provide a tuple.
Rebuild indexes during sync correctly
This picks up a fix in repc which would cause indexes to sometimes not get built correctly during sync.
v2.0.0
Improvements
- You can now scan indexes starting at a particular key
- Scanning indexes was fixed to work with indexes larger than a few hundred items
Breaking API Changes
ScanOptions
is now flattened to deal with thestartKey
andstartKeyExclusive
- We now return a tuple for the key when scanning over indexes
See https://replicache-sdk-js.now.sh/interfaces/readtransaction.html#scan for more information.
v1.0.0
v0.9.0: Bump version to 0.9.0.
- Had to skip past 0.7.0 and 0.8.0 due to unpublished versions on npm
- Scan now works for more than one page with indexes (rocicorp/repc#231)
- Remove noisy console.debug() statements that were logging every RPC (they were messing up our perf tests)
- Rename ScanId -> ScanKey and id to key. Deprecate old names but allow them to be used still
- This is the first release that is BSL
v0.6.0
- Initial support for indexes. See https://replicache-sdk-js.now.sh/interfaces/writetransaction.html#createindex and https://github.com/rocicorp/replicache-sdk-js/blob/master/sample/lit-todo/main.js#L64
- Initial GC implementation!