@expo/spawn-async 1.5.0
A Promise-based interface into processes created by child_process.spawn
@expo/spawn-async@1.5.0 was published on 2019-05-30. 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 >=4.
All @expo/spawn-async versions · Permanent reference to 1.5.0 · Latest release
Package specifications
| Version | 1.5.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-05-30T12:27:13.069Z |
| Node.js requirement | >=4 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 28.89 KiB |
| Published file count | 10 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @expo/spawn-async 1.5.0
npm install @expo/spawn-async@1.5.0 pnpm add @expo/spawn-async@1.5.0 yarn add @expo/spawn-async@1.5.0
Runtime dependencies
- cross-spawn ^6.0.5
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.
- cross-spawn@6.0.6 — direct
- isexe@2.0.0 — indirect
- nice-try@1.0.5 — indirect
- path-key@2.0.1 — indirect
- semver@5.7.2 — indirect
- shebang-command@1.2.0 — indirect
- shebang-regex@1.0.0 — indirect
- which@1.3.1 — indirect
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
- https://registry.npmjs.org/%40expo%2Fspawn-async/1.5.0 — retrieved 2026-10-29T10:46:03.586Z
- https://api.deps.dev/v3/systems/npm/packages/%40expo%2Fspawn-async/versions/1.5.0 — retrieved 2026-10-29T10:46:04.108Z
- https://api.deps.dev/v3/systems/npm/packages/%40expo%2Fspawn-async/versions/1.5.0:dependencies — retrieved 2026-10-29T10:46:04.123Z