Sergey

The curious thing — after page refresh, the DB is ok and I can access to read and write 🤔

@rshigg I think your issue is not connected with this. I had the same error, and here is the solution https://github.com/jlongster/absurd-sql/issues/14#issuecomment-902116794 . You need to set up the correct CORS

I think the issue is connected with this https://github.com/jlongster/absurd-sql/issues/24 . Cause after an increase of page size the frequency of such error got lower

I also noticed that such error happens when I have intensive writing in one tab, and intensive reading in a separate tab (everything happens at the same time) 🤔

Ok, I found, at least when it happens — when IndexedDB is resizing. So, if you put 100,000 records in db, and then delete them — this error will never...

@rhashimoto good discover 👍

@jlongster yep, I can do that. But I am not sure about the deadlines, cause right now I am pretty busy

@steida I am waiting for when https://github.com/jlongster/absurd-sql/pull/36 PR will be merged, then I will open another PR where I will be working on typescript support. I would be happy to...

For vite it's better to do: ``` import absurdSqlWasmUrl from "@jlongster/sql.js/dist/sql-wasm.wasm?url"; let SQL = await initSqlJs({ locateFile: () => absurdSqlWasmUrl, }); ``` For CRA: ``` import sqlWasmUrl from "@trong-orm/sql.js/dist/sql-wasm.wasm"; let...

Multiple open tabs scenario I guess