title: Compress to tar.gz on Grunt
body: <p>This is driving me crazy, I'm just trying to compress a folder like:</p>
  
  <pre><code>tar -czvf app.tar.gz ./app/
  </code></pre>
  
  <p>an obviously it works just fine, but <a href="https://npmjs.org/package/grunt-shell" rel="nofollow">https://npmjs.org/package/grunt-shell</a> produces a corrupted tar.gz:</p>
  
  <pre><code>shell: {
    deploy: {
      command: 'tar -czvf app.tar.gz ./app/'
    }
  }
  </code></pre>
  
  <p>I've tried <a href="https://npmjs.org/package/grunt-contrib-compress" rel="nofollow">https://npmjs.org/package/grunt-contrib-compress</a> without luck (and I prefer to use the shell one because after the compression I'll do another thing with the tar.gz).</p>
  
  <p>My stack:</p>
  
  <p>OSX                    10.8.3<br>
  node                   0.10.4<br>
  Grunt                  0.4.1<br>
  grunt-shell            0.2.2<br>
  grunt-contrib-compress 0.5.0  </p>
  
  <p><strong>Thanks to @hereandnow78 for point out the sequence thing!</strong></p>
  
  <p>If you have:</p>
  
  <pre><code>shell: {
    deploy: {
      command: 'tar -cfvz app.tar.gz ./app/'
    }
  },
  </code></pre>
  
  <p>Then it'll give you a tar.gz file called "vz" (without extension) with the right content.</p>
  
  <p>But, if you have:</p>
  
  <pre><code>shell: {
    deploy: {
      command: 'tar -czf app.tar.gz ./app/'
    }
  },
  </code></pre>
  
  <p>Then it works as expected... So the issue comes from the verbose param, maybe it has something to do with using stdout for the verbose info?</p>
  
  <p>What is really annoying is that <code>tar -czvf app.tar.gz ./app/</code> works just fine outside the grunt task.</p>
  
  <p><strong>Would someone please clarify this?</strong></p>