@vercel/fs-detectors 5.4.8
Vercel filesystem detectors
@vercel/fs-detectors@5.4.8 was published on 2025-07-16. Its manifest declares 8 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @vercel/fs-detectors versions · Permanent reference to 5.4.8 · View npm registry JSON · Latest release
Package specifications
| Version | 5.4.8 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2025-07-16T13:51:09.696Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 8 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 111.65 KiB |
| Published file count | 35 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./dist/index.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @vercel/fs-detectors 5.4.8
npm install @vercel/fs-detectors@5.4.8 pnpm add @vercel/fs-detectors@5.4.8 yarn add @vercel/fs-detectors@5.4.8
Runtime dependencies
- glob 8.0.3
- json5 2.2.2
- semver 6.3.1
- js-yaml 4.1.0
- minimatch 3.1.2
- @vercel/frameworks 3.7.2
- @vercel/error-utils 2.0.3
- @vercel/routing-utils 5.1.1
Peer requirements
- None declared
Optional dependencies
- None declared
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.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T23:40:27.822Z