Skip to content

Commit

Permalink
Updated link to other packages in readme
Browse files Browse the repository at this point in the history
  • Loading branch information
james-pre committed Nov 25, 2024
1 parent 02f4646 commit 0bc97a1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,13 @@ It works using a system of backends, which are used by ZenFS to store and retrie
ZenFS is modular and extensible. The core includes some built-in backends:

- `InMemory`: Stores files in-memory. This is cleared when the runtime ends (e.g. a user navigating away from a web page or a Node process exiting)
- `Overlay`: Use read-only file system as read-write by overlaying a writable file system on top of it. ([copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write))
- `Overlay`: Use a read-only file system as read-write by overlaying a writable file system on top of it. ([copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write))
- `Fetch`: Downloads files over HTTP with the `fetch` API (_readonly_)
- `Port`: Interacts with a remote over a `MessagePort`-like interface (e.g. a worker)

ZenFS supports a number of other backends. Many are provided as separate packages under `@zenfs`. More backends can be defined by separate libraries by extending the `FileSystem` class and providing a `Backend` object.

You can find all of the packages available over at [zenfs.dev](https://zenfs.dev).
You can find all of the packages available over on [NPM](https://www.npmjs.com/org/zenfs).

As an added bonus, all ZenFS backends support synchronous operations. All of the backends included with the core are cross-platform.

Expand Down

0 comments on commit 0bc97a1

Please sign in to comment.