@aztec/sqlite3mc-wasm 5.0.0-rc.2 → 5.0.1

package/dest/index.js

@@ -2,4 +2,27 @@
  * Re-exports sqlite3mc's ES module default (sqlite3InitModule) and the TypeScript types expected by downstream
  * consumers. Mirrors the `@sqlite.org/sqlite-wasm` package default export — sqlite3mc is a strict API-compatible
  * superset, so upstream types apply unchanged.
- */ export { default } from '../vendor/jswasm/sqlite3.mjs';
+ *
+ * BUNDLER COMPATIBILITY: SQLite3MultipleCiphers 2.3.5 stopped shipping the `-bundler-friendly` build variant, so
+ * this entry re-exports the plain `sqlite3.mjs`. That loader always resolves `sqlite3.wasm` through its
+ * `Module['locateFile']` hook, which computes `new URL(path, import.meta.url)` with a *dynamic* `path` — invisible
+ * to bundlers, so bundled consumers request an unhashed `sqlite3.wasm` relative to the emitted chunk and 404 at
+ * runtime (pre-2.3.5, the bundler-friendly variant carried a statically-analyzable reference instead). To stay
+ * bundler-friendly we wrap the init and inject `emscriptenLocateFile` — the vendored loader's supported escape
+ * hatch (`Module['locateFile']` defers to it when present on the init-module state) — resolving the wasm via a
+ * static `new URL('…/sqlite3.wasm', import.meta.url)` that bundlers detect, emit, and rewrite. Unbundled usage is
+ * unaffected: the static URL resolves to the real vendored path.
+ */ import sqlite3InitModuleUnwrapped from '../vendor/jswasm/sqlite3.mjs';
+/** Statically analyzable wasm reference: bundlers emit the asset and rewrite this URL to its final location. */ const SQLITE3_WASM_URL = new URL('../vendor/jswasm/sqlite3.wasm', import.meta.url);
+const sqlite3InitModule = (...args)=>{
+    // `sqlite3.mjs` creates `globalThis.sqlite3InitModuleState` at import time and the inner Emscripten factory
+    // captures it (and deletes the global) on init, binding it as `this` of `Module['locateFile']`. Mutate the live
+    // object; recreate it if a previous init already consumed it (`debugModule` must exist — the factory calls it).
+    const g = globalThis;
+    const state = g.sqlite3InitModuleState ??= Object.assign(Object.create(null), {
+        debugModule: ()=>{}
+    });
+    state.emscriptenLocateFile = (path, prefix)=>path === 'sqlite3.wasm' ? SQLITE3_WASM_URL.href : new URL(path, prefix || import.meta.url).href;
+    return sqlite3InitModuleUnwrapped(...args);
+};
+export default sqlite3InitModule;

package/dest/src/index.d.ts

@@ -2,7 +2,19 @@
  * Re-exports sqlite3mc's ES module default (sqlite3InitModule) and the TypeScript types expected by downstream
  * consumers. Mirrors the `@sqlite.org/sqlite-wasm` package default export — sqlite3mc is a strict API-compatible
  * superset, so upstream types apply unchanged.
+ *
+ * BUNDLER COMPATIBILITY: SQLite3MultipleCiphers 2.3.5 stopped shipping the `-bundler-friendly` build variant, so
+ * this entry re-exports the plain `sqlite3.mjs`. That loader always resolves `sqlite3.wasm` through its
+ * `Module['locateFile']` hook, which computes `new URL(path, import.meta.url)` with a *dynamic* `path` — invisible
+ * to bundlers, so bundled consumers request an unhashed `sqlite3.wasm` relative to the emitted chunk and 404 at
+ * runtime (pre-2.3.5, the bundler-friendly variant carried a statically-analyzable reference instead). To stay
+ * bundler-friendly we wrap the init and inject `emscriptenLocateFile` — the vendored loader's supported escape
+ * hatch (`Module['locateFile']` defers to it when present on the init-module state) — resolving the wasm via a
+ * static `new URL('…/sqlite3.wasm', import.meta.url)` that bundlers detect, emit, and rewrite. Unbundled usage is
+ * unaffected: the static URL resolves to the real vendored path.
  */
-export { default } from '../vendor/jswasm/sqlite3.mjs';
+import sqlite3InitModuleUnwrapped from '../vendor/jswasm/sqlite3.mjs';
+declare const sqlite3InitModule: typeof sqlite3InitModuleUnwrapped;
+export default sqlite3InitModule;
 export type { Database, SAHPoolUtil, Sqlite3Static } from '@sqlite.org/sqlite-wasm';
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiaW5kZXguZC50cyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9pbmRleC50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQTs7OztHQUlHO0FBQ0gsT0FBTyxFQUFFLE9BQU8sRUFBRSxNQUFNLDhCQUE4QixDQUFDO0FBQ3ZELFlBQVksRUFBRSxRQUFRLEVBQUUsV0FBVyxFQUFFLGFBQWEsRUFBRSxNQUFNLHlCQUF5QixDQUFDIn0=
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiaW5kZXguZC50cyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9pbmRleC50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiQUFBQTs7Ozs7Ozs7Ozs7Ozs7R0FjRztBQUNILE9BQU8sMEJBQTBCLE1BQU0sOEJBQThCLENBQUM7QUFVdEUsUUFBQSxNQUFNLGlCQUFpQixFQUFFLE9BQU8sMEJBVy9CLENBQUM7QUFFRixlQUFlLGlCQUFpQixDQUFDO0FBQ2pDLFlBQVksRUFBRSxRQUFRLEVBQUUsV0FBVyxFQUFFLGFBQWEsRUFBRSxNQUFNLHlCQUF5QixDQUFDIn0=

package/dest/src/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,OAAO,EAAE,OAAO,EAAE,MAAM,8BAA8B,CAAC;AACvD,YAAY,EAAE,QAAQ,EAAE,WAAW,EAAE,aAAa,EAAE,MAAM,yBAAyB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,OAAO,0BAA0B,MAAM,8BAA8B,CAAC;AAUtE,QAAA,MAAM,iBAAiB,EAAE,OAAO,0BAW/B,CAAC;AAEF,eAAe,iBAAiB,CAAC;AACjC,YAAY,EAAE,QAAQ,EAAE,WAAW,EAAE,aAAa,EAAE,MAAM,yBAAyB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aztec/sqlite3mc-wasm",
-  "version": "5.0.0-rc.2",
+  "version": "5.0.1",
   "type": "module",
   "exports": {
     ".": {

package/src/index.ts

@@ -2,6 +2,39 @@
  * Re-exports sqlite3mc's ES module default (sqlite3InitModule) and the TypeScript types expected by downstream
  * consumers. Mirrors the `@sqlite.org/sqlite-wasm` package default export — sqlite3mc is a strict API-compatible
  * superset, so upstream types apply unchanged.
+ *
+ * BUNDLER COMPATIBILITY: SQLite3MultipleCiphers 2.3.5 stopped shipping the `-bundler-friendly` build variant, so
+ * this entry re-exports the plain `sqlite3.mjs`. That loader always resolves `sqlite3.wasm` through its
+ * `Module['locateFile']` hook, which computes `new URL(path, import.meta.url)` with a *dynamic* `path` — invisible
+ * to bundlers, so bundled consumers request an unhashed `sqlite3.wasm` relative to the emitted chunk and 404 at
+ * runtime (pre-2.3.5, the bundler-friendly variant carried a statically-analyzable reference instead). To stay
+ * bundler-friendly we wrap the init and inject `emscriptenLocateFile` — the vendored loader's supported escape
+ * hatch (`Module['locateFile']` defers to it when present on the init-module state) — resolving the wasm via a
+ * static `new URL('…/sqlite3.wasm', import.meta.url)` that bundlers detect, emit, and rewrite. Unbundled usage is
+ * unaffected: the static URL resolves to the real vendored path.
  */
-export { default } from '../vendor/jswasm/sqlite3.mjs';
+import sqlite3InitModuleUnwrapped from '../vendor/jswasm/sqlite3.mjs';
+
+/** Statically analyzable wasm reference: bundlers emit the asset and rewrite this URL to its final location. */
+const SQLITE3_WASM_URL = new URL('../vendor/jswasm/sqlite3.wasm', import.meta.url);
+
+type SqliteInitModuleState = {
+  emscriptenLocateFile?: (path: string, prefix: string) => string;
+  debugModule?: (...args: unknown[]) => void;
+};
+
+const sqlite3InitModule: typeof sqlite3InitModuleUnwrapped = (...args) => {
+  // `sqlite3.mjs` creates `globalThis.sqlite3InitModuleState` at import time and the inner Emscripten factory
+  // captures it (and deletes the global) on init, binding it as `this` of `Module['locateFile']`. Mutate the live
+  // object; recreate it if a previous init already consumed it (`debugModule` must exist — the factory calls it).
+  const g = globalThis as { sqlite3InitModuleState?: SqliteInitModuleState };
+  const state = (g.sqlite3InitModuleState ??= Object.assign(Object.create(null), {
+    debugModule: () => {},
+  }));
+  state.emscriptenLocateFile = (path: string, prefix: string) =>
+    path === 'sqlite3.wasm' ? SQLITE3_WASM_URL.href : new URL(path, prefix || import.meta.url).href;
+  return sqlite3InitModuleUnwrapped(...args);
+};
+
+export default sqlite3InitModule;
 export type { Database, SAHPoolUtil, Sqlite3Static } from '@sqlite.org/sqlite-wasm';