title: CSS-PURGE: Config is getting ignored
body: <p>I try to use CSS-PURGE as system as a service to just notify a user if something could have been done better in his or her CSS. Thus I want CSS-PURGE to give me a report, which should work with the following configuration:</p>
  
  <pre><code>{
    "options": {
      "generate_report": true,
      "report_file_location": "purged_css_report_data.json"
    }
  }
  </code></pre>
  
  <p>I saved this code in a <code>config_css.json</code> and placed it in the project document root. Then, from the same directory, I used the following test command:</p>
  
  <pre><code>css-purge -d -c ".color { color: #ffffff; color: #ff0000; }"
  </code></pre>
  
  <p>The <code>-d</code> parameter is described in the documentation:</p>
  
  <blockquote>
    <p>-d: run with the default config file (config_css.json must exist in folder)</p>
  </blockquote>
  
  <p>I also tried the <code>-f</code> parameter with both relative and absolute path:</p>
  
  <pre><code>css-purge -f "config_css.json" -c ".color { color: #ffffff; color: #ff0000; }"
  css-purge -f "/path/to/project/config_css.json" -c ".color { color: #ffffff; color: #ff0000; }“
  </code></pre>
  
  <p>However, there is no generated report and when I add additional options to the config JSON they don’t affect the execution. It looks like the config is not being loaded.</p>
  
  <p>Am I doing something wrong here to don’t get CSS-PURGE generating a report or might there something be broken on their end?</p>