file-system-access
Dexie.js
file-system-access | Dexie.js | |
---|---|---|
16 | 33 | |
641 | 10,764 | |
0.6% | 1.2% | |
5.0 | 9.2 | |
about 1 month ago | 18 days ago | |
Bikeshed | JavaScript | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
file-system-access
-
The web just gets better with Interop 2024
You can read about the privacy concerts the community group published [1].
[1]: https://wicg.github.io/file-system-access/#privacy-considera...
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
WHATWG File System Standard provides a means to write directories and files to the private origin storage associated with a Web page origin. If you want you can use WICG File System Access API to write data directly to your filesystem in the browser. WHATWG File System Standard uses the same FileSystemDirectoryHandle and FileSystemFileHandle defined by File System Access API.
-
How to execute arbitrary dynamic shell scripts from and read output in the browser
Chromium-based browsers support File Systeam Access API.
-
"Can't open files in this folder because it contains system files"
We have stopped using the file system access API: https://github.com/WICG/file-system-access/issues/401
-
SQLite WASM in the Browser Backed by the Origin Private File System
Where file handling is concerned, there are at least
- File System Access API, https://wicg.github.io/file-system-access/
- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....
- Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessH...
There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.
-
Learn Postgres at the Playground
Huh. Disregard what I wrote entirely, then. Reading through https://github.com/WICG/file-system-access/blob/main/AccessH..., I can see how they’ve bypassed most of the problems I saw—I was making unnecessary assumptions.
Thank you for correcting me.
-
The State of WebAssembly 2022
> Browsers have never let anything (not even JS) have raw access to the host FS
I'm not sure what you mean by "raw access", but the File System Access API certainly allows web applications to do a lot of things.
> The File System Access API (formerly known as Native File System API and prior to that it was called Writeable Files API) enables developers to build powerful web apps that interact with files on the user's local device, like IDEs, photo and video editors, text editors, and more.
https://web.dev/file-system-access/
> After a user grants a web app access, this API allows the app to read or save changes directly to files and folders on the user’s device. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents. Additionally, web apps can use this API to store references to files and directories they’ve been given access to, allowing the web apps to later regain access to the same content without requiring the user to select the same file again.
> Additionally this API also makes it possible for websites to get access to some directory without having to first prompt the user for access.
https://wicg.github.io/file-system-access/
It's not just a draft, it's been part of Chrome since version 78 in 2019.
> After a user grants access, this API allows web apps to read or save changes directly to files and folders on the user's device. It does all this by invoking the platform's own open and save dialog boxes.
https://blog.chromium.org/2019/09/chrome-78-beta-new-houdini...
Discussion at the time:
https://news.ycombinator.com/item?id=21032537
-
How to Persist Web App Data in the User File System?
In the post, the Vite webserver is only used to serve the HTML and JS static files to the browser. When the user saves or opens text files, the code uses the web File System Access API (https://wicg.github.io/file-system-access/) to interact with the user file system.
-
The road to universal JavaScript
Have you heard of Project Fugu and their idea of a File System Access API in the browser? https://wicg.github.io/file-system-access/
-
What's your prefered way to allow end user to rename multiple text files?
I don't know a C++ equivalent of HTML , prompt(), or File System Access API (https://wicg.github.io/file-system-access/; https://web.dev/file-system-access/) using JavaScript in the browser window.
Dexie.js
-
Ask HN: Wa-SQLite vs. Dexie, 2024
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?
- Dexie.js – Minimalistic IndexedDB Wrapper
- Dexie.js: A Minimalistic Wrapper for IndexedDB
- Koji wrapper koristiti za IndexedDB?
-
A comprehensive guide to making your web app feel native
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.
-
Best way to store persistent data?
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.
-
Database in Chrome Extension?
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.
-
IndexedDB on steroids using Dexie.js
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.
-
Better Ways To Handle Data Storage on The Web Client
If you are just looking for a solution for your IndexedDB needs I find Dexie to be one of the best but depending on other needs, the others in the list are also good to consider.
What are some alternatives?
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.
brave-browser - Brave browser for Android, iOS, Linux, macOS, Windows.
PouchDB - :koala: - PouchDB is a pocket-sized database.
webusb - Connecting hardware to the web.
WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
fs - File System Standard
idb - IndexedDB, but with promises
standards-positions
sql.js - A javascript library to run SQLite on the web.
construct-stylesheets - API for constructing CSS stylesheet objects
store.js - Cross-browser storage for all use cases, used across the web.