vscode-live-server VS Dexie.js

I think your using the VSCode Live Server plugin. I would not use the Live Server plugin to run your app. The plugin does some magic to inject additional HTML into displayed page. Having SVG icons breaks it (not sure if you are using svg icons). I would run a basic app through a Python server by creating pyServer.py file:

Now open the html file using an HTTP server of your choice. I'm using the Live Server VS Code extension. You will see something like this.

More than likely.

This seems like a common issue with the vs code live server extension. You may want to switch to using npm live-server or try setting a proxy: https://github.com/ritwickdey/vscode-live-server/blob/master/docs/settings.md

I was using the VS code live server extension from here https://github.com/ritwickdey/vscode-live-server which exposes port 5500 on my localhost by default.

You need to use a server that establishes a root directory to /build (not fall back to the root of C:). I tried to get LiveServer (VS Code Extension) to function but it too needs the server root set to /build. Just found this which should solve that problem.

After downloading it, I will also recommend downloading an extension called Live Server in VsCode and it will help you to create a local server and view the changes made to the website without refreshing it each time & is super useful, Trust me!

To set the hostname to the desired IP address, use liveServer.settings.host (the default is 127.0.0.1).

Dexie.js

The word on the street is that https://github.com/rhashimoto/wa-sqlite is nearly production ready, closing in on the neat 1.0.0 release, with its IDBBatchAtomic engine highly recommended at https://www.powersync.com/blog/sqlite-persistence-on-the-web. You can try out the benchmark https://rhashimoto.github.io/wa-sqlite/demo/benchmarks.html.

And the other contestant is Dexie, stable https://dexie.org/.

If you were to branch into a new venture today, which one would you pick? And why?

That said, there are some great ways to wrap IndexedDB to make it easier to work with. Since I’m writing this article I’ll toss in my local-first framework Verdant, which can be used without the sync features as a standalone IndexedDB-powered database with a type-safe schema and deployable data migrations. For a lighter-weight approach, maybe check out Dexie.

Using IndexedDB. I have heard its pretty cumbersome to use. There are wrappers like Dexie.js but I am not sure if it works seamlessly with Tauri or if it is the correct thing for my use case.

I use IndexedDB, specifically the idb library (https://github.com/jakearchibald/idb), or Dexie.js (https://dexie.org/) if you are more novice. This works great for large sets of data. For smaller amounts, Chrome Storage API will do.

To make things easier, Dexie.js provides a straightforward and simplified process of creating databases, storing data, updating data and database migrations, etc., over the top of indexedDB.