From 26870bcdf2196bdcbcac083a17e9e7517a5cef5c Mon Sep 17 00:00:00 2001
From: Christopher Serr <christopher.serr@gmail.com>
Date: Fri, 1 May 2020 14:57:35 +0200
Subject: [PATCH] Disambiguate the import in the WASM bindings

It seems like wasm-bindgen generates both `livesplit_core_bg.wasm` as
well as a `livesplit_core_bg.js` now. We used to import from
`livesplit_core_bg` in our bindings before, which is now ambiguous.
---
 livesplit-core                 | 2 +-
 src/type-definitions/wasm.d.ts | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 src/type-definitions/wasm.d.ts

diff --git a/livesplit-core b/livesplit-core
index 4cb9747..d911478 160000
--- a/livesplit-core
+++ b/livesplit-core
@@ -1 +1 @@
-Subproject commit 4cb9747ed1c15ae341cf44e32725ce3ebc960b0a
+Subproject commit d911478e9db2f4fb1b8cb529a2ad00902bbd4ab4
diff --git a/src/type-definitions/wasm.d.ts b/src/type-definitions/wasm.d.ts
new file mode 100644
index 0000000..d2a6ba4
--- /dev/null
+++ b/src/type-definitions/wasm.d.ts
@@ -0,0 +1 @@
+declare module '*.wasm'