fs
secure-file-transfer
| fs | secure-file-transfer | |
|---|---|---|
| 7 | 1 | |
| 207 | 0 | |
| 3.4% | - | |
| 6.8 | 0.0 | |
| 3 months ago | about 1 year ago | |
| HTML | ||
| GNU General Public License v3.0 or later | MIT License |
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.
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
secure-file-transfer
-
I spent two years building a desktop environment that runs in the browser, it's finally in beta!
Use any means necessary to transfer your data across devices. Could be IPFS, could be FTP, could be EventSource, WebSocket, WebTransport, Fetch, whatever. See https://github.com/guest271314/secure-file-transfer; offscreen-webrtc, https://github.com/paullouisageneau/libdatachannel.
What are some alternatives?
node-postgres - PostgreSQL client for node.js.
file-system-access - Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
goyo.vim - :tulip: Distraction-free writing in Vim
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
runno - Browser-based runtime for programming languages and WASI binaries.
datasette-lite - Datasette running in your browser using WebAssembly and Pyodide
standards-positions
construct-stylesheets - API for constructing CSS stylesheet objects
file-handling - API for web applications to handle files
absurd-sql - sqlite3 in ur indexeddb (hopefully a better backend soon)
daedalOS - Desktop environment in the browser