@photostructure/fs-metadata 1.2.0 → 1.3.0

package/doc/SECURITY_AUDIT_2026.md

@@ -190,6 +190,7 @@ A caller could theoretically provide a malicious pattern causing ReDoS.
 **Files**: `src/windows/volume_mount_points.cpp`, `src/windows/volume_metadata.cpp`, `src/windows/system_volume.h`
 
 **Issue**: `GetVolumeInformationW` was called redundantly:
+
 - In `volume_mount_points.cpp`: once for `fstype`/`isReadOnly`, then again inside `IsSystemVolume()`
 - In `volume_metadata.cpp`: `IsSystemVolume()` queried the API, then `VolumeInfo` queried it again 5 lines later
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@photostructure/fs-metadata",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "Cross-platform native filesystem metadata retrieval for Node.js",
   "homepage": "https://photostructure.github.io/fs-metadata/",
   "types": "./dist/index.d.ts",

package/src/index.ts

@@ -122,7 +122,9 @@ export function getVolumeMetadata(
  */
 export function getVolumeMetadataForPath(
   pathname: string,
-  opts?: Partial<Pick<Options, "timeoutMs" | "linuxMountTablePaths">>,
+  opts?: Partial<
+    Pick<Options, "timeoutMs" | "linuxMountTablePaths" | "mountPoints">
+  >,
 ): Promise<VolumeMetadata> {
   return getVolumeMetadataForPathImpl(
     pathname,
@@ -148,7 +150,9 @@ export function getVolumeMetadataForPath(
  */
 export function getMountPointForPath(
   pathname: string,
-  opts?: Partial<Pick<Options, "timeoutMs" | "linuxMountTablePaths">>,
+  opts?: Partial<
+    Pick<Options, "timeoutMs" | "linuxMountTablePaths" | "mountPoints">
+  >,
 ): Promise<string> {
   return getMountPointForPathImpl(
     pathname,

package/src/types/options.ts

@@ -1,5 +1,7 @@
 // src/types/options.ts
 
+import type { MountPoint } from "./mount_point";
+
 /**
  * Configuration options for filesystem operations.
  *
@@ -7,6 +9,18 @@
  * @see {@link OptionsDefault} for the default values
  */
 export interface Options {
+  /**
+   * Pre-fetched mount points to use instead of querying the system.
+   *
+   * When provided, functions like {@link getMountPointForPath} and
+   * {@link getVolumeMetadataForPath} will use these mount points for device ID
+   * matching instead of calling {@link getVolumeMountPoints} internally. This
+   * avoids redundant system queries when resolving multiple paths.
+   *
+   * Obtain via `getVolumeMountPoints({ includeSystemVolumes: true })` — system
+   * volumes must be included for device ID matching to work correctly.
+   */
+  mountPoints?: MountPoint[];
   /**
    * Timeout in milliseconds for filesystem operations.
    *

package/src/volume_metadata.ts

@@ -235,10 +235,12 @@ export async function findMountPointByDeviceId(
   nativeFn: NativeBindingsFn,
 ): Promise<string> {
   const targetDev = resolvedStat.dev;
-  const mountPoints = await getVolumeMountPointsImpl(
-    { ...opts, includeSystemVolumes: true },
-    nativeFn,
-  );
+  const mountPoints =
+    opts.mountPoints ??
+    (await getVolumeMountPointsImpl(
+      { ...opts, includeSystemVolumes: true },
+      nativeFn,
+    ));
 
   const prefixMatches: string[] = [];
   const deviceMatches: string[] = [];