Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review CLI options #59

Open
paulyoung opened this issue Apr 26, 2015 · 1 comment
Open

Review CLI options #59

paulyoung opened this issue Apr 26, 2015 · 1 comment
Milestone

Comments

@paulyoung
Copy link
Contributor

See if any are missing on the v4 branch that should be part of it.

@paulyoung paulyoung added this to the v4.0 milestone Apr 26, 2015
@mtscout6
Copy link
Member

For reference the old options are:

✗ ./node_modules/.bin/blessc --help
Usage: blessc [options] [ source | - ] [destination]

Options :
  -v, --version      print version
  -h, --help         print this help
  -f, --force        overwrite input file
  -x, --compress     "minify" @import
  --no-cleanup       don't remove old css file before overwriting
  --no-imports       disable @import on stylesheets
  --no-cache-buster  turn off the cache buster

Full documentation can be found at http://blesscss.com/

The current state of v4 is:

./bin/blessc --help
BlessCSS v4.0.0-alpha.1 - Tools to ensure CSS files meet IE 6-9 selector limit restrictions.

Commands:
  count  checks an existing css file and fails if the selector count exceeds IE limits
  chunk  breaks up css file to multiple files if it exceeds IE selector limits

Options:
  --version, -v  Show version number  [boolean]

Examples:
  bin/blessc count <file|directory>
  bin/blessc count <file|directory> --no-color
  bin/blessc chunk <input file|directory>   (chunked files will reside next to input css files with the format *.##.css)
  bin/blessc chunk <input file|directory> --out-dir <output directory>
  bin/blessc chunk <input file|directory> --sourcemaps

For additional information see http://blesscss.com

Since the goal of this tool is solely to deal with selector counts I don't see why we should need the compress, cleanup, of cache-buster options. That sounds like the responsibility of a higher level tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants