For Flutter Web, should sqlite3.wasm and drift_worker.js versions match the sqlite3 and drift packages in pubspec.lock?

[mohansella]

I lost a few hours debugging an issue before realizing that the versions of sqlite3.wasm and drift_worker.js likely need to match the versions of the sqlite3 and drift packages in my pubspec.lock.

Following the documentation here:
https://drift.simonbinder.eu/platforms/web/#prerequisites

…I initially used the latest available sqlite3.wasm and drift_worker.js, which didn’t work in my setup. After rechecking everything, I realized this was most likely caused by a version mismatch.

This was my mistake and probably due to my lack of experience with Flutter and Drift, but I wanted to share the feedback.

If matching versions is a requirement, could this be:
• documented more explicitly, and/or
• considered as a feature request to automatically copy the correct sqlite3.wasm and drift_worker.js files during the build process?

This might help others avoid similar confusion.

[simolus3]

Thanks for raising this, and sorry for the confusion here!

I do my best to make both workers and the sqlite3.wasm file forwards-compatible, meaning that upgrading drift or the sqlite3 package without upgrading your workers and WebAssembly assets should still work. So you don't always have to watch your pubspec.lock to ensure you're using the exact same version.

The inverse is not true, however. If you use a sqlite3.wasm from version x, the version of package:sqlite3 must be at least that version. This is likely what has caused these issues for you. In particular, for the major upgrade from 2.x -> 3.x in the sqlite3 package, there is no compatibility between the two versions.

Drift is still using version 2.x of the sqlite3 package for now. So if you've downloaded a sqlite3.wasm for version 3.x, those wouldn't work.

documented more explicitly

I have added a note to those releases explaining that now.

considered as a feature request to automatically copy the correct sqlite3.wasm and drift_worker.js files during the build process?

Builders shouldn't download anything, so this is tricky to do at the moment. I hope we'll have something for this in the future (dart-lang/native#988), but a manual download (or perhaps a script invocation) is the best approach we have for now.

[dickermoshe]

A friend of mine had the same thing happen to him. The documentation should be updated

[simolus3]

858a6b8 adds a note to the docs.