#IndexedDB
- IndexedDB to store non-serializable values (like the currently open FileSystemFileHandle).
- Web Workers for binary manipulation and expensive compute.
- Popover API for accessible hint/popover-like elements.
- <dialog> for native, accessible, and stylable modals and dialogs.
October 31, 2025 at 1:39 PM
IndexedDB is likely the only way you can persist non-serializable data across sessions.

That's the tweet.
October 24, 2025 at 8:20 PM
Just released Ordinality — a framework-agnostic migration tool for Browser, Node, and Deno.

We use it in production on both backend and frontend.

Ordinality works with any database — IndexedDB, SQL, state files, or anything else.

github.com/vitonsky/ord...

#opensource #javascript
October 22, 2025 at 6:11 PM
TIL: if you store in IndexedDB a granted FileSystemX handler you should als store with it options because if you close and reopen the browser, or create a new session, that handler will not work unless you check again against its permissions.
Only then it prompts: once or always?
October 23, 2025 at 10:51 AM
If capitalists were honest. 😆
October 20, 2025 at 12:16 AM
Wenn der Texter deines Cookie Banners 1 ehrliche Haut ist
October 19, 2025 at 1:51 PM
Built a video player that recovers last position using IndexedDb.

Code: github.com/joshnuss/sk-...
October 19, 2025 at 3:44 PM
Day 79 of building Pixelshot, an AI product photography app

✅ Implemented IndexedDB so everything loads super fast
✅ Payments and subscriptions are done

I might add AI edit and enhancer before the MVP but need to figure out the credits system

#buildinpublic
October 14, 2025 at 6:47 PM
storing an image Blob:

Service worker cache: failed ❌
OPFS: failed ❌
localStorage: hacky
IndexedDB: success ✅

This is entirely Tauri's fault (well... my fault for trying to wrap a PWA in a native app - maybe there is a lesson here?)
October 14, 2025 at 10:02 AM
I wonder if you could use proxies to take the client API and fake it out? Maybe with indexeddb? So you can still use a lexicon that doesn't exist yet but it'd just be stored locally
October 12, 2025 at 10:00 PM
Новинки Chrome 141. Ускорение IndexedDB с методом getAllRecords(), обновление WebRTC Encoded Transform V2 вслед за спекой, поддержка атрибутов и свойств width и height для вложенных SVG, Proofreader API и обновления CSP в origin trials и другие. #chrome #browser

developer.chrome.com/release-note...
October 10, 2025 at 10:30 AM
You could get around the money and privacy issues with a webapp that does its own fetching and stores all data in the browser (via indexeddb). No server – or user accounts – needed :)

Syncing between devices would require a sync service (icloud etc.) though, which is the same as it does now
October 8, 2025 at 3:05 PM
idk man apple doesn't seem to want to fix a lot of web app related stuff. this indexeddb bug in webkit has been around for a long time and it's a pretty big one

www.google.com/search?q=Unk...
October 7, 2025 at 12:53 AM
After a few hours tinkering I'm convinced my new fav way to prototype is web components and a local IndexedDB w/ a Dexie abstraction layer. No frameworks, no closed-box 'magic', portable in case your fav AWS reseller turns out to be owned by a fascist-loving bootlicking wasteman. Very fun and cool.
October 3, 2025 at 9:08 AM
今日のZennトレンド

CompressionStream でブラウザで gzip 圧縮する
この記事では、モダンなブラウザが提供するCompressionStreamとDecompressionStream APIを利用して、JavaScript上でgzip圧縮と解凍ができるようになったことを説明しています。
これにより、pakoやzlib.jsなどの外部ライブラリが不要になり、ブラウザネイティブで高速な圧縮・解凍が可能になります。
主な活用例として、IndexedDBへのデータ保存時のストレージ容量削減や、S3やDuckDBなどのAPIとの連携が挙げられています。
CompressionStream でブラウザで gzip 圧縮する
モダンなブラウザは JS API として gzip や deflate が使えます。昔から Chrome に搭載してるのは知ってたんですが、今見たらだいたい搭載してました。https://developer.mozilla.org/ja/docs/Web/API/DecompressionStreamhttps://compression.spec.whatwg.org/#decompressio
zenn.dev
September 4, 2024 at 9:17 PM
IndexedDB内で簡潔する、Webページに対するメモをぱっと残せるブックマークレットを作った。ブックマークレットなので、必要な環境は(モダン)ブラウザとお気に入り登録のみ。

完全ドローカル運用。一応申し訳程度にjsonファイルへのエクスポート/インポート機能で別ブラウザや別PCにデータを持っていくことはできる。

生成AI使うとこういうちょっとしたものを試しにつくる、が爆速だな。
December 14, 2024 at 1:11 PM
The full collaborative state is stored both locally in the browser in IndexedDB and in SQLite on the sync server (you can use the cloud service endpoint or run the backend yourself via `npx jazz-run sync`). In React, you can then just subscribe to value changes and everything updates automatically.
February 27, 2025 at 1:52 PM
funny how we're circling back to sqlite in web again after we replaced websql for indexeddb
June 26, 2024 at 12:51 AM
Thinking about whether we can push duckdb-wasm to spill to disk somewhere ~ either OPFS or IndexedDB. This would increase the boundaries of what is possible with DuckDB in the browser (even if it'll be slow, at least it won't destroy the page due to memory out of bounds issues!)
October 26, 2024 at 1:26 PM
I’ve been messing with indexeddb in the browser — now looking for another gratuitous use.
December 18, 2024 at 9:59 PM
Care about IndexedDB read performance ⚡?

Check out Edge’s getAllRecords proposal, which allows for fast batch reads in either directions ➡️ https://patrickbrosset.com/articles/2024-11-19-even-faster-indexeddb-reads-with-getallrecords/

Feedback on the explainer is more than welcome!
November 20, 2024 at 9:08 AM
Also ArchiveWeb exclusively stores pages in IndexedDB. I have like a hundred GB worth from ArchiveWeb alone. It can export to a fairly standard format for this type of project, but that has to be done... from the browser. and it takes a LOOONG time with how big the archives are.
June 21, 2025 at 8:19 PM
August 24, 2025 at 1:26 PM
MothNote 먼 미래에 IndexedDB 생각했는데 unlimitedStorage 로 제한 해제되면 쓸 이유가 없을듯? 웹 연동 싱크 정도 먼 미래에 고려를
August 30, 2025 at 2:46 PM