Missing cli options in new postcss cli

[hyperknot]

I am trying to migrate from autoprefixer-cli to postcss-cli, however two options are really missing there:

1. autoprefixer -h: Where can I get a help specific to --use autoprefixer? I cannot imagine how can a new cli interface not support package specific help functions. It should work like git help rebase, etc.
2. autoprefixer -c: How can I clean a file now?

[ai]

You can clean files by set a empty array of browsers.

Maybe we should add some examples to Autoprefixer README. PR is welcome.

[ai]

@code42day what do you think about some cli.help in any plugin dir?

[ai]

Close this because anyway I will left old CLI https://github.com/ai/autoprefixer-cli

[iBobik]

In the current CLI are other examples of missing options.

Helps of new and old:

Usage: autoprefixer [OPTION...] FILES

Parse CSS files and add prefixed properties and values.

Options:
  -b, --browsers BROWSERS  add prefixes for selected browsers
  -c, --clean              remove all known prefixes
  -o, --output FILE        set output file
  -d, --dir DIR            set output dir
  -m, --map                generate source map
      --no-map             skip source map even if previous map exists
      --no-inline-map      do not inline maps to data:uri
      --inline-map         force inline map
      --annotation PATH    change map location relative from CSS file
      --no-map-annotation  do not add source map annotation comment in CSS
      --no-sources-content remove origin CSS from maps
      --sources-content    force include origin CSS into map
      --no-cascade         do not create nice visual cascade of prefixes
      --no-remove          do not remove outdated prefixes
      --safe               try to fix CSS syntax errors
  -i, --info               show selected browsers and properties
  -h, --help               show help text
  -v, --version            print program version

Files:
  If you didn't set input files, autoprefixer will read from stdin stream.

  By default, prefixed CSS will rewrite original files.

  You can specify output file or directory by '-o' argument.
  For several input files you can specify only output directory by '-d'.

  Output CSS will be written to stdout stream on '-o -' argument or stdin input.

Source maps:
  On '-m' argument Autoprefixer will generate source map for changes near
  output CSS (for out/main.css it generates out/main.css.map).

  If previous source map will be near input files (for example, in/main.css
  and in/main.css.map) Autoprefixer will apply previous map to output
  source map.

Browsers:
  Separate browsers by comma. For example, '-b "> 1%, opera 12"'.
  You can set browsers by global usage statictics: '-b "> 1%"'.
  or last version: '-b "last 2 versions"'.

Usage: /usr/local/bin/postcss -use plugin [--config|-c config.json] [--output|-o
output.css] [input.css]

Options:
  -c, --config       JSON file with plugin configuration
  -u, --use          postcss plugin name (can be used multiple times)
  --local-plugins    lookup plugins in current node_modules directory
  -o, --output       Output file (stdout if not provided)
  -d, --dir          Output directory
  -r, --replace      Replace input file(s) with generated output       [boolean]
  -s, --syntax       Alternative input syntax parser
  -p, --parser       Alternative CSS parser
  -t, --stringifier  Alternative output stringifier
  -w, --watch        auto-recompile when detecting source changes
  -v, --version      Show version number                               [boolean]
  -h, --help         Show help                                         [boolean]

Examples:
  postcss --use autoprefixer -c             Use autoprefixer as a postcss plugin
  options.json -o screen.css screen.css
  postcss --use autoprefixer                Pass plugin parameters in
  --autoprefixer.browsers "> 5%" -o         plugin.option notation
  screen.css screen.css
  postcss -u postcss-cachify -u             Use multiple plugins and multiple
  autoprefixer -d build *.css               input files

I thing, there should be wiki document explaining differences and how to migrate.

[iBobik]

I forgot to mention the second help is generic postcss help, help for specific autoprefixer CLI options not found.

[ai]

@iBobik do you want to write this wiki doc?

[iBobik]

I am not the right person, I use it just through Drupal module Less.

Jan Pobořil
http://honza.poboril.cz/

1. 10. 2015 v 8:01, Andrey Sitnik notifications@github.com:

@iBobik do you want to write this wiki doc?

—
Reply to this email directly or view it on GitHub.