automerge/automerge-js
2022-08-26 14:15:01 -05:00
..
config some api changes/tweaks - basic js package 2022-05-31 13:49:18 -04:00
examples/webpack move types to their own package 2022-05-27 10:23:51 -07:00
src automerge-js adding trace to out of date errors 2022-08-26 14:15:01 -05:00
test add getBackend to automerge-js 2022-06-16 17:49:32 -04:00
.eslintignore tslint to eslint 2022-05-22 13:53:11 -04:00
.eslintrc.cjs tslint to eslint 2022-05-22 13:53:11 -04:00
.gitignore fix some typescript errors - depricate default export of the wasm package 2022-08-11 18:24:21 -05:00
index.d.ts fix some typescript errors - depricate default export of the wasm package 2022-08-11 18:24:21 -05:00
LICENSE able to build npm package 2022-05-22 13:53:11 -04:00
package.json fix ownKeys bug in automerge-js 2022-08-11 18:49:42 -05:00
README.md Fixup js edit-trace script and documentation bits 2022-07-07 09:25:45 +01:00
tsconfig.json clean up lint, simplify package, hand write an index.d.ts 2022-05-23 19:04:31 +02:00
tslint.json convert automerge-js to typescript 2022-05-22 13:53:11 -04:00

Automerge JS

This is a reimplementation of Automerge as a JavaScript wrapper around the "automerge-wasm".

This package is in alpha and feedback in welcome.

The primary differences between using this package and "automerge" are as follows:

  1. The low level api needs to plugged in via the use function. The only current implementation of "automerge-wasm" but another could used in theory.
import * as Automerge from "automerge-js";
import * as wasm_api from "automerge-wasm";

// browsers require an async wasm load - see automerge-wasm docs
Automerge.use(wasm_api);
  1. There is no front-end back-end split, and no patch format or patch observer. These concepts don't make sense with the wasm implementation.

  2. The basic Doc<T> object is now a Proxy object and will behave differently in a repl environment.

  3. The 'Text' class is currently very slow and needs to be re-worked.

Beyond this please refer to the Automerge README for further information.