Phantomas

This release introduces metrics reporting to [statsd](https://github.com/etsy/statsd/) daemon. Implementing 10 took quite a while, but it's finally completed :)

phantomas can now be provided with `--tablet` or `--phone` option that will force viewport and user agent settings specific for a given device - 213.

All metrics were ported to the "offenders" framework. It should now be lot easier to understand what can be changed to improve given metric.

HTTP redirects are considered webperf bottlenecks. A new metric has been added to measure the time spent on redirects - 211.

More details can be found below.

Bug fix
- 194 - Analysing CSS fails on Windows

This release introduces phantomas as CommonJS module that can be used directly from your nodejs project. Read more in [API docs](https://github.com/macbre/phantomas/wiki/npm-module) and in 152.

Other improvements and new features:
- running `phantomas -h` will now print out nice usage help
- phantomas supports "native" PhantomJS options to be passed when running a report. Setting HTTP proxy (`--proxy`) or providing JAR file for storing cookies (`--cookies-file`) is now possible.
- CSS analyzing script is now developed as a [separate project](https://github.com/macbre/analyze-css) (it's of course still used when `--analyze-css` option is passed)
- phantomas can now wait for a given element being present on the page (via CSS selector) - 144
- when being run in [Travis CI](https://travis-ci.org/) environment phantomas will fold the output - 141
- thanks to 167 more metrics emit its specific information as offenders instead of notices

Files layout has changed a bit. `phantomas.js` "binary" is now located in `bin/` directory. Please update your symlinks if you're pointing directly to git checkout. Users of npm package should not notice this change at all.

Grunt plugin

And last, but not least. stefanjudis created [phantomas plugin for Grunt](https://npmjs.org/package/grunt-phantomas) that gathers and visualizes historical webperf data - [an example](http://stefanjudis.github.io/grunt-phantomas/gruntjs/). Definitely worth checking!

Changelog

New metrics
- 111 - Report outdated CSS prefixes
- 166 - Add "X-cache: PASS" support in cacheHits module (by kennydee)

Improvements
- 139 - Allow specifying Http Proxy (reported by heynemann)
- 141 - Add Travis folds to output (LaurentGoderre)
- 144 - Wait for a given CSS selector before generating a report
- 163 - Passing through Phantomjs options (as suggested by plasticine)
- 167 - Port modules to offenders framework
- 178 - Use PhantomJS native cookie JAR support
- 184 - Adding --film-strip-dir param to configure film strip output dir (by iNem0o)

Bug fixes
- 160 - phantomas.getDOMPath throws 'null' is not an object (evaluating 'node.nodeName')

Internals
- 152 - node.js module for spawning phantomas process and getting results
- 161 - Use optimist npm module for handling phantomas options
- 169 - Integrate analyze-css npm module
- 185 - Structure cleanup
- 187 - Create async queue that will trigger reports generation

Trivia

_[ Fantômas contre Scotland Yard](http://www.imdb.com/title/tt0060400/)_

Bug fix
- 165 - `--viewport` arguments are reversed (thanks indeox for reporting)

This release changes the way PhantomJS is invoked. Instead of running it directly, `phantomas.js` script uses node.js to spawn PhantomJS process. This allows locally installed PhantomJS to be used for running phantomas. Thanks shama for the idea and LaurentGoderre for implementing it.

Suggestions that phantomas generate should now be better structured, thanks to a feature ~~stolen from~~ inspired by [YSlow](http://yslow.org/phantomjs/). Read more about offenders in 140.

New features have been added, including:
- `phantomas.setMarkerMetric` allows you to measure times relative to `responseEnd` event (i.e. measured since the arrival of the last byte of HTML) - 119
- by passing `--screenshot` option you can generate a screenshot of fully loaded page that phantomas is run for - 125
- latency (i.e. time to first byte) related metrics - 134
- thanks to cphoover phantomas now supports persistent cookie jar - 149

And last, but not least. Phantomas has been described in [an article for Performance Calendar 2013](http://calendar.perfplanet.com/2013/phantomas/).

New metrics
- 134 - Add latency related metrics

Improvements
- 112 - Ability to run phantomas locally (by shama)
- 125 - Make a screenshot when the page is fully loaded
- 126 - Document how to set up site performance monitoring using phantomas and tap-eater
- 128 - Allow asserts to be provided via command-line options
- 149 - Adding support for persistant cookies via cookie jar argument. (by cphoover)
- 151 - Modified to use the local phantomjs instead of the global one. (by LaurentGoderre)

Bug fixes
- 129 - phantomas should die with an error code when the page timeouts
- 131 - Target URL should be reported when a redirect is received
- 147 - package.json: specifying devDependencies as array is deprecated
- 156 - phantomas.getDOMPath throws 'undefined' is not a function (evaluating 'node.className.trim())

Internals
- 119 - Add phantomas.setMarkerMetric
- 140 - Introduce "offenders" framework

Trivia

_[Fantômas se déchaîne](http://www.imdb.com/title/tt0059168/)_

This release adds a completely new use case to phantomas - **web performance monitoring**.

Using a simple "asserts framework" you can specify maximum values for metrics (108). After setting up asserts, you can render results of phantomas run using [TAP format](http://testanything.org/wiki/index.php/Main_Page) (94 and 127). And then [plug them into Continous Integration system](http://www.slideshare.net/guest94ab56d/2013-0717continuous-performancemonitoringwithjenkins) of your choice (e.g. Jenkins) or use [simple command-line program](https://github.com/macbre/tap-eater) to report metrics not meeting the limits.

Support for JUnit format is planned for the upcoming releases - 93.

Two experimental feature were added:
- passing `--film-strip` option will create a serie of screenshots when page is being loaded (89).
- `onDOMReadyEnd` and `windowOnLoadTimeEnd` metrics were added (88). They report when handling of onDOMReady and windowOnLoad events is completed.

Oh, one more thing. You can provide `--disable-js` and see how faster your site loads with JavaScript disabled (115). And what needs to be improved in your JS code ;)

New metrics
- 88 - Add onDOMReadyEnd and windowOnLoadTimeEnd metrics

Improvements
- 89 - Register film strip when page is loading
- 94 and 127 - Add TAP format with details using YAMLish format
- 107 - Reporting jsErrors backtrace for format json and plain
- 108 - Introduce "metrics asserts"
- 115 - Make it possible to disable JavaScript on the page
- 120 - Simple phantomas asserts runner

Bug fixes
- 105 - "False error" when running performance on a site without jQuery?
- 117 - `onDOMReadyTime` and `windowOnLoadTime` should be calculated relative to the first response being received
- 122 - Requests to blocked domains are included in stats

Internals
- 113 - Introduce formatters interface

Trivia

_[Fantômas contre Fantômas](http://www.imdb.com/title/tt0143247/)_