Unhandler error event about tmi

[addyosmani]

This should be fixed in master now. @igrigorik if you get a chance, could you give it another spin?

$ npm install git://github.com/addyosmani/tmi -g

[igrigorik]

works!

QQ, trying it on nytimes:

On Mobile:
You have more image bytes than 60% of sites
+955 kB compared to sites in the 25th percentile
+712 kB compared to sites in the 50th percentile
+198 kB compared to sites in the 75th percentile

Results are a bit confusing to me. First, it says the site is in the 60th quantile, but if so, why is +198KB for 75th percentile? That would imply that the site is 75th+ percentile.

Also, minor nitpick: KB not kB (1024 vs 1000 :)).

[Tenzer]

I can confirm that installing the package from master solves the problem.

[addyosmani]

@igrigorik It looks like my calculations were a little askew there. I'm going to pull out support for the "You have more images than N" output to the next minor release so it can properly be fixed :) For now we'll have:

$ tmi http://redrobin.com

Your image weight: 3.55 MB
Median mobile site image weight: 660 kB
Median desktop site image weight: 1.21 MB

On Mobile:
+3.49 MB compared to sites in the 25th percentile
+3.25 MB compared to sites in the 50th percentile
+2.73 MB compared to sites in the 75th percentile


On Desktop:
+3.41 MB compared to sites in the 25th percentile
+2.94 MB compared to sites in the 50th percentile
+2.14 MB compared to sites in the 75th percentile

Is that okay? The KB -> kB formatting is due to a formatting module we're using, but I'll open an upstream issue with the author to address that :)

[inadarei]

Master works but NPM version still throws errors. Can you please re-publish? Thanks.

[ashumeow]

Compiler told me that 'gpagespeed' module is missing. :|
I am also having issues with NPM though 👎

[addyosmani]

@ashumeow is this against master or the version on npm that you're seeing that exception thrown? I'm unable to repro locally but would like to confirm before pushing a new release.

[addyosmani]

After a fresh clone followed by npm install && npm link on a new machine:

[ashumeow]

@addyosmani Yeah! You're right.