moxystudio/node-cross-spawn

Issues

• [ERR_REQUIRE_ESM]: require() of ES Module

  #168 opened 2 months ago by 0xTheProDev
  2

• apple m1 throw error

  #152 opened 2 years ago by scZhengChao
  1

• CVE-2024-21538 | Regular Expression Denial of Service (ReDoS) in cross-spawn | Version Fixed?

  #167 opened 3 months ago by Scc33
  4

• Backport GHSA-3xgq-45jj-v275

  #165 opened 3 months ago by G-Rath
  2

• Cannot update cross-spawn@7.0.5

  #164 opened 3 months ago by wick3ds0ul
  1

• 7.0.4 release breaks windows

  #163 opened 3 months ago by achingbrain
  3

• I get different results using mac terminals and using cross-spawn

  #159 opened 7 months ago by qiaolin-li
  0

• Error: spawn rm ENOENT

  #157 opened a year ago by bhaireshm
  2

• is cross-spawn has asynchronous method ?

  #153 opened a year ago by dimaslanjaka
  2

• error is null

  #151 opened 2 years ago by steinybot
  0

• Please add switch to opt-out of special ENOENT behavior for Windows if desired

  #104 opened 6 years ago by mattflix
  10

• The command itself is not properly escaped

  #150 opened 3 years ago by mnpenner
  0

• process.version is undefined

  #149 opened 3 years ago by Shujee
  2

• In Windows, spawn.kill() doesn't kill child process

  #148 opened 3 years ago by localhosted
  0

• EBADF: bad file descriptor, uv_pipe_open on windows with ipc

  #137 opened 5 years ago by kratoon
  1

• Block or remove please

  #147 opened 3 years ago by weyyserabut
  0

• Stop Child Process on SIGINT

  #145 opened 3 years ago by meilechwieder
  1

• windowsHide option

  #143 opened 4 years ago by q2s2t
  0

• double quotes in arguments

  #141 opened 4 years ago by jssuttles
  4

• spawnSync freezes

  #140 opened 4 years ago by bernardoadc
  0

• Support ~ (tilde) in PATH

  #139 opened 4 years ago by bersbersbers
  0

• Node.js spawn results in ENOENT on Termux/Android

  #138 opened 4 years ago by Leif-W
  0

• Publish as global package?

  #129 opened 5 years ago by afzalsayed96
  0

• use unix tools if available in windows

  #136 opened 5 years ago by 1000i100
  0

• Use the `/q` flag with `cmd.exe`

  #135 opened 5 years ago by zenflow
  0

• Cannot download v7.0.3

  #134 opened 5 years ago by elinskytap
  3

• Does not work inside workers threads with custom current working directory

  #130 opened 5 years ago by Lakitna
  4

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

  #122 opened 6 years ago by busticated
  1

• Does not work inside workers threads

  #124 opened 5 years ago by luizfelipe94
  5

• Drop support for versions below Node.js 6

  #108 opened 5 years ago by Siilwyn
  6

• How to store the value of a command?

  #120 opened 6 years ago by amiteshore
  2

• Improper documentation

  #119 opened 6 years ago by jimitpatel
  2

• Wrong detection under yarn on windows

  #111 opened 6 years ago by GongT
  1

• An in-range update of babel-preset-moxy is breaking the build 🚨

  #105 opened 6 years ago by greenkeeper
  1

• Child process hangs

  #96 opened 7 years ago by annakocheshkova
  14

• How do I run an npm command with NPM_TOKEN?

  #95 opened 7 years ago by morgs32
  2

• Paths with NTFS JUNCTIONS (links)

  #78 opened 7 years ago by SteveALee
  7

• path.normalize(command) breaks local command on rebased cwd

  #90 opened 7 years ago by evocateur
  4

• Bad escaping when an argument has quotes followed by a pipe

  #82 opened 7 years ago by satazor
  1

• Support option to mirror exit status

  #88 opened 7 years ago by AndersDJohnson
  5

• Cannot resolve dependency 'spawn-sync'

  #87 opened 7 years ago by jerrygreen
  3

• Possible issue with pre-commit + npm + spawn env

  #80 opened 7 years ago by sudo-suhas
  5

• Commands with spaces fail with shell: true

  #77 opened 7 years ago by imgx64
  2

• An in-range update of rimraf is breaking the build 🚨

  #79 opened 7 years ago by greenkeeper
  1

• An in-range update of lru-cache is breaking the build 🚨

  #74 opened 8 years ago by greenkeeper
  0

• spawn inputs console warnings into stdout stream

  #70 opened 8 years ago by joadr
  4

• An in-range update of eslint is breaking the build 🚨

  #59 opened 8 years ago by greenkeeper
  6

• child_process.spawn shell option is available in Node v5 and v4 too

  #68 opened 8 years ago by claudiopro
  0

• An in-range update of rimraf is breaking the build 🚨

  #62 opened 8 years ago by greenkeeper
  1

• spawn.sync result object has `result.status == 0` for `result.signal == SIGKILL`

  #61 opened 8 years ago by brandones
  1