Version 3.51.1-build1 breaks sqlite3.wasm file resolution on Vite

[jurerotar]

After upgrading sqlite-wasm package to the 3.51.1-build1 version, internal import of the actual sqlite3.wasm file no longer works properly. The issue is that vite adds a hash to sqlite3.wasm file during build (you get something like sqlite3-abcd.wasm), but sqlite3.mjs still attempts to resolve file name without the hash. Attempting to use locateFile also doesn't solve this issue.

I've prepared a replication using your vite example: https://stackblitz.com/edit/vitejs-vite-w5cmvvub

Because the issue only happens during build, run vite build && vite preview.
You'll see the following error in the console:

The issue is here. Vite generated the following files:

Opening a network tab reveals that requested file does not include a hash, however.

I've attempted to fix this by using the locateFile function. There's a reproduction of that available here: https://stackblitz.com/edit/vitejs-vite-itfiv34f, you can reproduce by following the same instructions as in the first example.

Live example and the actual code I used to encounter this issue is available here:

• worker: https://github.com/jurerotar/Pillage-First-Ask-Questions-Later/blob/test/sqlite-3-51-error/app/(public)/(game-worlds)/(create)/workers/create-new-game-world-worker.ts,
• live reproduction: https://test-sqlite-3-51-error--pillagefirst.netlify.app/game-worlds/create

You can recreate the issue by clicking on the "Create server" button and opening the console.

Edit: updated reproduction urls

[tomayac]

Can you try the latest build and be sure to follow the vite usage instructions?

[jurerotar]

Thank you for publishing a new build! I've tried it out, but it doesn't work for me. It fails with the same issue. I don't need to set the headers, because I'm using SAHPool VFS, but I've tried setting them regardless and there's no difference (which makes sense, since it fails to resolve the actual wasm file).

I've done some digging and compared the differences between 3.50.4-build1 and latest build. bundler-friendly script, which was previously the entry point, was removed in version 3.51.0. Comparing the actual scripts, there's this one difference I believe is causing this issue:

sqlite-wasm/sqlite-wasm/jswasm/sqlite3.mjs

Lines 62 to 64 in 6d4953a

	Module['locateFile'] = function (path, prefix) {
	return new URL(path, import.meta.url).href;
	}.bind(sIMS);

This declaration was not present before and if I try removing it locally, building and then running the project, it seems to work as expected. This is expected, since this appears to be overriding locateFile function.

In my code, I'm doing this to retrieve the proper filename:

import sqliteWasmUrl from '@sqlite.org/sqlite-wasm/sqlite3.wasm?url';

const sqlite3 = await sqlite3InitModule({
  locateFile: () => sqliteWasmUrl,
});

Might it make sense to replace the declaration with this?:

if(!Module['locateFile']) {
  Module['locateFile'] = function (path, prefix) {
    return new URL(path, import.meta.url).href;
  }.bind(sIMS);
}

[tomayac]

Let's loop in @sgbeal from the SQLite team regarding possible changes between those versions.