--autoprefixer.browsers 'last ... versions' breaks on windows

It looks like autoprefixer relies on bash-specific syntax (or at least nx-specific syntax) for its autoprefix.browsers flag that lets you specify how many versions to support. As this affects all devs that have to work on cross-platform codebases that rely on either autoprefixer or even postcss in general, this feels like something worth examining to see if the bash syntax can be turned into something node can execute instead (since node’s API is guaranteed cross-platform compatible)

Minimal broken example:

input.css

body {
  margin: 0;
  padding: 0;
}

package.json

{
  "name": "test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "with": "postcss --use autoprefixer --autoprefixer.browsers 'last 3 versions' -o result.css input.css",
    "without": "postcss --use autoprefixer -o result.css input.css"
  },
  "author": "",
  "license": "PD",
  "dependencies": {
    "autoprefixer": "^6.4.0",
    "postcss-cli-simple": "^1.0.1"
  }
}

Guaranteed broken on Windows 7, 8, 8.1 and 10 (not tested older versions, as only Vista SP2 is not EOL yet, but I will horribly generalize and say I don’t really expect anyone on Vista to be a node developer…):

$> npm run with

Not broken:

$> npm run without

[DigitalVilla]

windows needs backslashes! this script is tested and it works. “prefix:css”: “postcss --use autoprefixer -b "last 10 versions" -o css/style.prefix.css css/style.css”

[Pomax]

Conclusion: windows only supports double quotes in the standard command interpreter for quoted arguments (singles quotes will not work), and because NPM scripts area already in double quotes, if you want quoted arguments in an NPM script, you need to escape your double quotes.

This is effectively a general cross-platform issue around NPM scripts that work in Windows as well as in linux/macos, rather than an autoprefixer or even postcss-cli issue.