8000 Improve README with "on top of stack" info · Issue #106 · uncss/grunt-uncss · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Improve README with "on top of stack" info #106
Open
@franz-josef-kaiser

Description

@franz-josef-kaiser

I just set up grunt-uncss alongside processhtml. Task order was:

  1. CSS Preprocessor > Cache folder
  2. UnCSS > Cache folder (again)
  3. Minify > Deploy folder

as it felt quite unnecessary to drop processhtml in just satisfy a workflow that I wasn't using, I tried running in the deploy folder on the minified result. And it was great, as the result was an even (slightly) smaller file. On top of that, I just dropped it into my stack/task list at the top/end and haven't had to modify anything just to fit it in. Now the task order is

  1. CSS Preprocessor > Cache folder
  2. Minify > Deploy folder
  3. UnCSS on minified file > Deploy folder

I'm in the opinion that an explanation about this (most basic and easy) usage should be added to the README.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0