file-system-access
fs
file-system-access | fs | |
---|---|---|
16 | 7 | |
641 | 207 | |
0.6% | 3.4% | |
5.0 | 6.8 | |
about 1 month ago | 3 months ago | |
Bikeshed | HTML | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
fs
-
persistent storage API on Firefox temporary extension
You can use File System Standard https://fs.spec.whatwg.org/ to write data for that origin (Firefox doesn't implement File System Access API, nonetheless a File object can still be written to local disk using File API).
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Both Firefox and Chromium (Chrome) have implemented WHATWG File System Standard.
-
SQLite WASM in the Browser Backed by the Origin Private File System
Can you just slow down for a moment and focus on what you said?
> We're literally in the discussion about File System API that is:
> - not on any standards track
As others have pointed out the standard is here:
https://fs.spec.whatwg.org/
> - considered harmful by other browser vendors
It is literally being drafted in conjunction by all the major browsers.
> - shipped by default in Chrome
So what? I for one am thankful that Chromium enables features earlier than other browsers. If you don't want the Chromium implementation then don't use it.
-
Show HN: I built a WASI playground for running CLI binaries in the browser
Score another point for memfs, the in-memory node.js fe impl.
WHATWG recently took up File System Access spec as their FS spec. It both looks semi promising, but they seem to only care about & are only building specs for specifically emscripten wasm users. Only sync apis, only usable from dedicated workers... there's some hopes for more latter but feels super weird to see the web finally get fs access & have it be fast... but for it to be extremely odd shaped hand tailored to a very narrow class of use.
https://fs.spec.whatwg.org/
- Learn Postgres at the Playground
What are some alternatives?
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
node-postgres - PostgreSQL client for node.js.
brave-browser - Brave browser for Android, iOS, Linux, macOS, Windows.
goyo.vim - :tulip: Distraction-free writing in Vim
webusb - Connecting hardware to the web.
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
standards-positions
runno - Browser-based runtime for programming languages and WASI binaries.
construct-stylesheets - API for constructing CSS stylesheet objects
wasmbuilder - Javascript package that helps to build wasm code by hand.