* feat: make vitest tests pass
* chore: update readme & add deno test for web bundle
* chore: bump version to 1.0.8-alpha.0
* chore: bump loro-crdt version
* fix: build script
export init method from loro-wasm/web
* chore: bump version
* chore: specify which files to include for npm publish
* refactor: rename loro-js to loro-js-test
* refactor: remove the old loro-js folder
* fix: build scripts
* chore: 1.0.8-alpha.3
* chore: add release info
This PR includes a BREAKING CHANGE.
It enables you to create containers before attaching them to the document, making the API more intuitive and straightforward.
A container can be either attached to a document or detached. When it's detached, its history/state does not persist. You can attach a container to a document by inserting it into an attached container. Once a container is attached, its state, along with all of its descendants's states, will be recreated in the document. After attaching, the container and its descendants, will each have their corresponding "attached" version of themselves?
When a detached container x is attached to a document, you can use x.getAttached() to obtain the corresponding attached container.
* refactor(wasm): extract VersionVector class and fix inconsistent PeerID in wasm
* fix: example type err
* fix: binding err
* fix: peer id repr should be consistent
* test: update tests
