Add travis-ci and npm badges to readme about tslint

[ashwinr]

great idea! I'll add the npm badge. Travis builds are timing out due to the git submodule dependency on typescript. I need to figure out a way to use the compiler without pulling in their sources for every build. Maybe I'll just revert to embedding their source within tslint.

[Bartvds]

Nice, I see the badge.

Git submodules are always a bit funky. When I clone your repo it does not automatically pull the submodule content, but instead I have to manually do a git.exe submodule update ....

Is that the correct way to do it?

If so you might want to look into an alternate solution: the submodule downloads the whole history for the TypeScript repos (check the typescript submodule folder; mine is over a gigabyte of data :)

[ashwinr]

yeah, it's not good. I started out with a static repo of TypeScript. submodules are nicer as you only have to update the commit pointer to the remote repo, but it has too much overhead. I'll look into a simpler solution. Either:

• clone the TypeScript repo locally (or)
• use the compiled tsc.js along with its definition file

[Bartvds]

It would be nice if contributors (and travis-ci) can work without having to pull the gigabytes of TypeScript repo, so the first option is not that attractive (maybe even less then the current submodule).

The second one would be neat if the TypeScript devs would check-in the definition file into npm.

Alternately you could manually export just the source files from the TypeScript repo into your own repos src-subfolder and check that in. It's not as nice as a real link but it would be a lot less data, and they don't update releases that often.

And if they do you just delete the current data and export the new code and let git sort out the changes. You might even roll a simple utility script to do just that (using an external TypeScript checkout as source).

[ashwinr]

Aaand the builds are green!

[Bartvds]

I see it, very awesome.