hack imports of wasm due to the issues in Vite and Next.js build systems

bindings/javascript/sync/packages/browser/index-turbopack-hack.ts

@@ -0,0 +1,32 @@
+import { setupMainThread } from "@tursodatabase/database-browser-common";
+import { tursoWasm } from "./wasm-inline.js";
+
+// Next (turbopack) has issues with loading wasm module: https://github.com/vercel/next.js/issues/82520
+// So, we inline wasm binary in the source code in order to avoid issues with loading it from the file
+const __wasmFile = await tursoWasm();
+
+export let MainWorker = null;
+
+const napiModule = await setupMainThread(__wasmFile, () => {
+  const worker = new Worker(new URL('./worker.js', import.meta.url), {
+    name: 'turso-database-sync',
+    type: 'module',
+  })
+  MainWorker = worker;
+  return worker
+});
+
+export default napiModule.exports
+export const Database = napiModule.exports.Database
+export const Statement = napiModule.exports.Statement
+export const Opfs = napiModule.exports.Opfs
+export const OpfsFile = napiModule.exports.OpfsFile
+export const connect = napiModule.exports.connect
+export const initThreadPool = napiModule.exports.initThreadPool
+export const GeneratorHolder = napiModule.exports.GeneratorHolder
+export const JsDataCompletion = napiModule.exports.JsDataCompletion
+export const JsProtocolIo = napiModule.exports.JsProtocolIo
+export const JsProtocolRequestBytes = napiModule.exports.JsProtocolRequestBytes
+export const SyncEngine = napiModule.exports.SyncEngine
+export const DatabaseChangeTypeJs = napiModule.exports.DatabaseChangeTypeJs
+export const SyncEngineProtocolVersion = napiModule.exports.SyncEngineProtocolVersion