@zenfs/core 2.2.0 → 2.2.2

package/dist/backends/single_buffer.js

@@ -710,7 +710,7 @@ export class SingleBufferStore extends BufferView {
         return this._fs;
     }
     set fs(fs) {
-        if (this.buffer instanceof SharedArrayBuffer)
+        if (this.buffer.constructor.name === 'SharedArrayBuffer')
             fs === null || fs === void 0 ? void 0 : fs.attributes.set('no_id_tables', true);
         this._fs = fs;
     }

package/dist/index.js

@@ -10,4 +10,5 @@ export * from './vfs/index.js';
 export { fs };
 import * as fs from './vfs/index.js';
 export default fs;
-globalThis.__zenfs__ = fs;
+import $pkg from '../package.json' with { type: 'json' };
+globalThis.__zenfs__ = Object.assign(Object.create(fs), { _version: $pkg.version });

package/dist/polyfills.js

@@ -1,7 +1,8 @@
 /* node:coverage disable */
-var _a, _b, _c;
+/* eslint-disable @typescript-eslint/unbound-method */
+var _a, _b, _c, _d;
+var _e;
 import { warn } from 'kerium/log';
-// eslint-disable-next-line @typescript-eslint/unbound-method
 (_a = Promise.withResolvers) !== null && _a !== void 0 ? _a : (Promise.withResolvers = (warn('Using a polyfill of Promise.withResolvers'),
     function () {
         let _resolve, 
@@ -17,4 +18,12 @@ import { warn } from 'kerium/log';
 (_b = Symbol['dispose']) !== null && _b !== void 0 ? _b : (Symbol['dispose'] = (warn('Using a polyfill of Symbol.dispose'), Symbol('Symbol.dispose')));
 // @ts-expect-error 2540
 (_c = Symbol['asyncDispose']) !== null && _c !== void 0 ? _c : (Symbol['asyncDispose'] = (warn('Using a polyfill of Symbol.asyncDispose'), Symbol('Symbol.asyncDispose')));
+function randomUUID() {
+    const bytes = crypto.getRandomValues(new Uint8Array(16));
+    bytes[6] = (bytes[6] & 0x0f) | 0x40;
+    bytes[8] = (bytes[8] & 0x3f) | 0x80;
+    const hex = [...bytes].map(b => b.toString(16).padStart(2, '0')).join('');
+    return `${hex.slice(0, 8)}-${hex.slice(8, 12)}-${hex.slice(12, 16)}-${hex.slice(16, 20)}-${hex.slice(20)}`;
+}
+(_d = (_e = globalThis.crypto).randomUUID) !== null && _d !== void 0 ? _d : (_e.randomUUID = (warn('Using a polyfill of crypto.randomUUID'), randomUUID));
 /* node:coverage enable */

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@zenfs/core",
-	"version": "2.2.0",
+	"version": "2.2.2",
 	"description": "A filesystem, anywhere",
 	"funding": {
 		"type": "individual",
@@ -81,10 +81,10 @@
 		"@types/eslint__js": "^8.42.3",
 		"c8": "^10.1.2",
 		"eslint": "^9.15.0",
-		"globals": "^15.9.0",
+		"globals": "^16.0.0",
 		"prettier": "^3.2.5",
 		"tsx": "^4.19.1",
-		"typedoc": "^0.27.1",
+		"typedoc": "^0.28.0",
 		"typescript": "^5.7.2",
 		"typescript-eslint": "^8.16.0"
 	}

package/readme.md

@@ -1,23 +1,28 @@
 # ZenFS
 
-ZenFS is a cross-platform library that emulates the [NodeJS filesystem API](http://nodejs.org/api/fs.html). It works using a system of backends, which are used by ZenFS to store and retrieve data. ZenFS can also integrate with other tools.
+ZenFS is a cross-platform library that emulates the [Node.js filesystem API](http://nodejs.org/api/fs.html).
+It works using a system of backends, which are used by ZenFS to store and retrieve data.
+ZenFS can also integrate with other tools.
 
 ## Backends
 
-ZenFS is modular and extensible. The core includes some built-in backends:
+ZenFS is modular and easily extended. 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)
-- `CopyOnWrite`: Use readable and writable file systems with ([copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write)).
+- `CopyOnWrite`: Use readable and writable file systems with [copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write).
 - `Fetch`: Downloads files over HTTP with the `fetch` API
 - `Port`: Interacts with a remote over a `MessagePort`-like interface (e.g. a worker)
 - `Passthrough`: Use an existing `node:fs` interface with ZenFS
 - `SingleBuffer`: A backend contained within a single buffer. Can be used for synchronous multi-threaded operations using `SharedArrayBuffer`
 
-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.
+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 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.
+As an added bonus, all ZenFS backends support synchronous operations.
+Additionally, all of the backends included with the core are cross-platform.
 
 For more information, see the [docs](https://zenfs.dev/core).
 
@@ -27,7 +32,9 @@ For more information, see the [docs](https://zenfs.dev/core).
 npm install @zenfs/core
 ```
 
-If you're using ZenFS, especially for big projects, please consider supporting the project. Thousands of hours have been dedicated to its development. Your acknowledgment or financial support would go a long way toward improving ZenFS and its community.
+If you're using ZenFS, especially for big projects, please consider supporting the project.
+Thousands of hours have been dedicated to its development.
+Your acknowledgment or financial support would go a long way toward improving ZenFS and its community.
 
 ## Usage
 
@@ -149,7 +156,7 @@ fs.umount('/mnt/zip'); // finished using the zip
 
 ### Devices and device files
 
-ZenFS includes experimental support for device files. These are designed to follow Linux's device file behavior, for consistency and ease of use. You can automatically add some normal devices with the `addDevices` configuration option:
+ZenFS includes support for device files. These are designed to follow Linux's device file behavior, for consistency and ease of use. You can automatically add some normal devices with the `addDevices` configuration option:
 
 ```ts
 await configure({
@@ -208,9 +215,9 @@ A huge thank you to [![Deco.cx logo](https://avatars.githubusercontent.com/deco-
 
 ## Building
 
-- Make sure you have Node and NPM installed. You must have Node v18 or newer.
+- Make sure you have Node and NPM installed. You must have Node v22 or newer.
 - Install dependencies with `npm install`
-- Build using `npm run build`
+- Build using `npx tsc` or `npm run build`
 - You can find the built code in `dist`.
 
 ### Testing