@react-native-windows/fs 0.73.1

A minimal-dependency drop-in replacement to `fs` with changes for resiliency, promises, and convenience.

@react-native-windows/fs@0.73.1 was published on 2024-04-26. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 18.

All @react-native-windows/fs versions · Permanent reference to 0.73.1 · Latest release

Package specifications

Version0.73.1
License declarationMIT
Published2024-04-26T22:41:52.514Z
Node.js requirement>= 18
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size165.21 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entrylib-commonjs/fs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars17360
Repository forks1210

Install @react-native-windows/fs 0.73.1

npm install @react-native-windows/fs@0.73.1
pnpm add @react-native-windows/fs@0.73.1
yarn add @react-native-windows/fs@0.73.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Security-Policy10/10 — security policy file detected
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License9/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies10/10 — all dependencies are pinned
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Fuzzing10/10 — project is fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness