# win-spawn

> Spawn for node.js but in a way that works regardless of which OS you're using

Latest version **2.0.0** (published 2013-08-01) · BSD license · 0 weekly downloads

> **Deprecated.** This package is deprecated.

## Install

```sh
npm install win-spawn
pnpm add win-spawn
yarn add win-spawn
bun add win-spawn
```

Provides the command `win-spawn`.

## Health

**Score 10/100 (F)** — status: deprecated.

Negative: deprecated.

## Facts

| | |
|---|---|
| Version | 2.0.0 |
| Published | 2013-08-01 |
| First published | 2012-09-19 |
| Weekly downloads | 0 |
| License | BSD |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 63 |
| Author | ForbesLindesay |
| Maintainers | forbeslindesay |

## Links

- npm: https://www.npmjs.com/package/win-spawn
- Repository: https://github.com/ForbesLindesay/win-spawn
- npm.io page: https://npm.io/package/win-spawn

## Recent versions

- 2.0.0 (latest) — 2013-08-01
- 1.1.2 — 2013-05-29
- 1.1.1 — 2013-02-04
- 1.1.0 — 2013-02-04
- 1.0.2 — 2013-01-31
- 1.0.1 — 2013-01-31
- 0.0.0 — 2012-09-19

## README

# win-spawn

  Spawn for node.js but in a way that works regardless of which OS you're using.  Use this if you want to use spawn with a JavaScript file.  It works by explicitly invoking node on windows.  It also shims support for environment variable setting by attempting to parse the command with a regex.  Since all modification is wrapped in `if (os === 'Windows_NT')` it can be safely used on non-windows systems and will not break anything.

## Installation

  $ npm install win-spawn

## Usage

### Command Line

  All the following will work exactly as if the 'win-spawn ' prefix was ommitted when on unix.

    $ win-spawn foo
    $ win-spawn ./bin/foo
    $ win-spawn NODE_PATH=./lib foo
    $ win-spawn NODE_PATH=./lib foo arg1 arg2

  You can also transform all the line endings in a directory from `\r\n` to `\n` just by running:

    $ win-line-endings

  You can preview the changes by running:

    $ win-line-endings -p

  It will ignore `node_modules` and `.git` by default, but is not clever enough to recognise binary files yet.

### API

This will just pass through to `child_process.spawn` on unix systems, but will correctly parse the arguments on windows.

```javascript
spawn('foo', [], {stdio: 'inherit'});
spawn('./bin/foo', [], {stdio: 'inherit'});
spawn('NODE_PATH=./lib foo', [], {stdio: 'inherit'});
spawn('NODE_PATH=./lib foo', [arg1, arg2], {stdio: 'inherit'});
```

![viewcount](https://viewcount.jepso.com/count/ForbesLindesay/win-spawn.png)

---
_Source: https://npm.io/package/win-spawn · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._