node-cross-spawn

node-cross-spawn copied to clipboard

Node.js spawn results in ENOENT on Termux/Android, despite the command (in my case, npm) being installed, and in the PATH found in process.env. The Termux devs claim this works correctly...

Leif-W

I use git-bash (like probably nearly all windows npm user). if i run mkdir -p plop it create me plop folder if not existant and do nothing if it exist....

1000i100

Is this an nodejs issue we can solve here in userland? https://github.com/nodejs/node/issues/27120 - Use the `/q` flag with `cmd.exe` in `child_process.spawn()` I think it makes sense to add the flag...

zenflow

`which` bin conflicts with native `which` when running npm scripts...

1

hey there :wave: thanks for a very helpful lib :pray::+1: i'm coming here by way of [execa](https://github.com/sindresorhus/execa) having hit upon a fairly gnarly edge-case: let's say you have a js...

busticated

apple m1 throw error

1

"use strict"; Object.defineProperty(exports, "__esModule", { value: true }); exports.spawnSafeSync = void 0; const cross_spawn_1 = require("cross-spawn"); const defaultOptions = { logStdErrOnError: true, throwOnError: true, }; const spawnSafeSync = (command, args,...

scZhengChao

The type from node child_process is: ``` interface SpawnSyncReturns { pid: number; output: Array; stdout: T; stderr: T; status: number | null; signal: NodeJS.Signals | null; error?: Error | undefined;...

steinybot

`verifyENOENT` function has 2 arguments (`status` and `parsed`) but there is code that calls `verifyENOENT` function with 3 arguments. So, I removed the last argument.

yinm

## feat: add type `async` export ## chore: remove `path-key` to internal function because `path-key` does not have `d.ts` ## [chore: split index.js to support ES import export](https://github.com/dimaslanjaka/node-cross-spawn/commit/a8020bf3c27f3519639c241b16cb4703373dd68f) - to...

dimaslanjaka

Error: spawn rm ENOENT

2

Below error found while executing rm command using spawn in windows Error: spawn rm ENOENT at notFoundError

bhaireshm

fix: cmd-shim not identified if placed outside `node_modules/.bin/`

1

I have a node executable installed globally with `npm i -g` . Because of this, the cmd-shim was not placed in `node_modules/.bin/`. On Windows, this caused `cross-spawn` to escape arguments...

patrickkfkan