From 1d9d9b478651f9d197c69e6946c6cf6be6619395 Mon Sep 17 00:00:00 2001 From: chee Date: Mon, 5 Aug 2024 20:34:25 +0100 Subject: [PATCH] Fix use of Automerge input in escape hatch code we `import {next as Automerge}` but then we were trying to use it as `next` rather than `Automerge` :) --- docs/library_initialization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/library_initialization.md b/docs/library_initialization.md index 0a286a9..0546b4c 100644 --- a/docs/library_initialization.md +++ b/docs/library_initialization.md @@ -138,7 +138,7 @@ import wasmUrl from "@automerge/automerge/automerge.wasm?url"; import { next as Automerge } from "@automerge/automerge/slim"; import { Repo } from `@automerge/automerge-repo/slim`; -await next.initializeWasm(wasmUrl) +await Automerge.initializeWasm(wasmUrl) // Now we can get on with our lives @@ -155,7 +155,7 @@ import { automergeWasmBase64 } from "@automerge/automerge/automerge.wasm.base64. import { next as Automerge } from "@automerge/automerge/slim"; import { Repo } from `@automerge/automerge-repo/slim`; -await next.initializeBase64Wasm(automergeWasmBase64) +await Automerge.initializeBase64Wasm(automergeWasmBase64) // Now we can get on with our lives const repo = new Repo({..})