Package: node-execa (6.1.0+dfsg1+~cs16.0.4-8)
better `child_process`
Other Packages Related to node-execa:
dep: [node-get-stream]
Get a stream as a string, buffer, or array
dep: [node-is-stream] (>= 3)
Check if something is a Node.js stream
dep: [node-merge-stream]
Create a stream that emits events from multiple other streams
dep: [node-mimic-fn] (>= 4)
Make a function mimic another one
dep: [node-npm-run-path] (>= 5.1.0+~4.0.0~)
Get your PATH prepended with locally installed binaries
dep: [node-shebang-command]
Get the command from a shebang
dep: [node-signal-exit] (>= 3.0.7~)
Fire an event no matter how a process exits
dep: [node-strip-eof] (>= 3.0.0-4~)
strip CR and LF characters from a string/buffer
dep: [node-which]
Cross-platform 'which' module for Node.js
Download node-execa
| Architecture | Package size | Installed size | Files | Package |
|---|---|---|---|---|
| all | 32 KiB | 168 KiB | list of files | Download |
Paketdateipfade (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.
Field source: Debian 12 (Bookworm) main amd64 revision bookworm-main-amd64:9e0b5aabb2465b3d2e7a7fe27f9913846277833f7a2826e7767acccff5b588c5