ThetaDev/automerge
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity
automerge/automerge-backend-wasm
History
Martin Kleppmann 7ae0edb283 Remove getChangesForActor from wasm backend 
This function no longer exists in the JS backend
2021-04-02 09:00:07 -07:00
..
src Remove getChangesForActor from wasm backend 2021-04-02 09:00:07 -07:00
test Add proptest for serialization 2021-01-14 12:30:25 -05:00
tests cargo fmt --all () 2020-11-08 14:47:18 +00:00
.gitignore reorg file for new package 2021-02-18 16:41:20 -05:00
Cargo.toml backend-wasm: Make yarn release work again () 2021-03-23 16:56:16 +00:00
GOALS_AND_ISSUES.md Update GOALS_AND_ISSUES.md 2020-04-16 11:31:08 -04:00
LICENSE tools for making an asmjs version 2020-04-05 10:22:45 -07:00
package.json reorg file for new package 2021-02-18 16:41:20 -05:00
package.mjs.json reorg file for new package 2021-02-18 16:41:20 -05:00
package.pkg.json reorg file for new package 2021-02-18 16:41:20 -05:00
README.md Fix types in wasm/README.md () 2021-03-27 11:12:50 +00:00
yarn.lock reorg file for new package 2021-02-18 16:41:20 -05:00

README.md

automerge-backend-wasm

This is a wrapper for the rust implementation of automerge-backend to be used with Automerge.

Using

You can require this synchronously as a CommonJS module or import it as a ES6 module

let Automerge = require("automerge")
let Backend = require("automerge-backend-wasm")
Automerge.setDefaultBackend(Backend)

import * as Automerge from "automerge"
import * as Backend from "automerge-backend-wasm"
Automerge.setDefaultBackend(Backend)

Note that the first uses a synchronous filesystem load of the wasm and will not be transferable to a browser bundle. The second uses ES6 wasm import statements which should work in all modern browsers but require a '--experimental-wasm-modules' flag on nodejs (v13 on) unless you pack/bundle the code into compatible format.