m19c/gulp-codeclimate-reporter

Send your coverage to codeclimate.

🤘🏽 Hello Stranger!

I'm a 36 years old Software Engineer from Ostermunich, Bavaria. My journey began when I was 14 years old. In a college in the middle of the mountains I decided to focus on building websites. The internet just turned 10 years old, almost nothing was available to kickstart a kid in programming. With a few printed sheets in my backpack I managed to kick things off. Since then, the passion never faded. At the moment I am working for Bayerischer Rundfunk (one of the biggest german broadcasters) and Kerngedanke (a social media content management system).

gulp-codeclimate-reporter's Issues

Windows support please?

I would be really grateful if you added some windows support.
This is basically what happens when I add this module into my gulp process on a windows machine

Command failed: C:\WINDOWS\system32\cmd.exe /s /c "CODECLIMATE_REPO_TOKEN=1234 node_modules/codeclimate-test-reporter/bin/codeclimate.js < "C:\callscreen\coverage\PhantomJS 2.0.0 (Windows 8 0.0.0)\lcov.info""
'CODECLIMATE_REPO_TOKEN' is not recognized as an internal or external command,
operable program or batch file.

I have all my servers on windows and so it would be really useful if this worked in windows, thanks.

I have to note that I can manually execute codeclimate and upload my lcov files but this is certainly missing :(

Transient qs dependency has a security vulnerability

Github alerts you about dependencies with security vulnerabilities, and I'm seeing one for [email protected], which comes from this repo in this way: gulp-codeclimate-reporter -> codeclimate-test-reporter -> request -> qs.

The newest version of codeclimate-test-reporter (0.5.0), however, uses a newer version of request, so fixing the issue would be as simple as npm i codeclimate-test-reporter@latest (barring incompatible API changes).

Thoughts?