"Constructors for derived classes must contain a 'super' call (But that call is in fact in place).

Happens for me as well. Copied a perfectly functioning class within a huge a project. Stripped it clean and renamed it. This will not sound logical at all, but within my project the error seems to be produced by calling a get-property of childitem within the
constructor. Funnily enough, this will also produce the same error on all other constructors following the one with the false error.

App.Data.Vessels is
public get Vessels(): someType[] { }

App and Data are both instantiated Classes, the later exposed as a get-Property within App.

as soon as i add
var list = App.Data.Vessels;
anywhere within my classes constructor (after super() of course), i get the false error.

The icing on the cake being: If i wrap the call within an anonymous function or a member function within the class i can call that function from within the constructor without the error being thrown....

Things seem to have stabilized now that I have installed today's 0.9.1.1 release but I haven't had much time today to evaluate the hotfix these problems. Initial impression is that the problems are fixed in 0.9.1.1. I'd suggest you upgrade and see if that
helps.

I installed 0.9.1.1. I have not yet seen any falsy errors, but I have not yet spend much time editing typescript in VS.

It didn't solve the "tsc.js(40468, 28) JavaScript runtime error: Unable to get property 'kind' of undefined or null reference " error.
But I spend some hours compile my typescript files with tsc, adding them one by one to the project, until I found the offending line.

The error is cause by the return statement. If I change that line to "return false;" or " return this.i > this.j" (declaring i and j as number), then the error does not occur.

But this does not occur when this is the only file in my project, but it occurs when I add it to my project containing 19 typescript files with about total 2800 lines of code and using 4 d.ts files (Kendo, JQuery, Modernirz, SignalR (last 3
from DefinitelyTyped))
So it is not reproducible in a small project. Maybe you have now some hints to search for the problem.

(If the helps you to reproduce, I can sent my files by e-mail to somebody of the team)

I try to get my project compiling with 0.9.1 (previously 0.8.3.1), but that appears not to be easy :-(.
I get several falsy errors:

Operator '<' cannot be applied to types 'number' and 'number'

above error also seen for > and == operators

Function 'xxx' declared a non-void return type, but has no return expression. (But the function has a void return type in the signature: function xxx() : void {})

Constructors for derived classes must contain a 'super' call (But that call is in fact in place).

Lots of errors on types in lib.d.ts saying: "All named properties must be subtypes of string indexer type 'any'"

Very weird.

I've had every single one of those errors (and more!) and I can assure you that each of those errors are completely bogus. Do not waste any of your time trying to eliminate them or debug them, they are NOT genuine errors at all. Basically the tsc compiler has
crapped out on something completely and utterly unrelated to the above, and those are just the cascading pile of errors that are served in the wake of the compiler bail out.

@PhotonStorm: I didn't spend any time on finding the cause of that error messages. It was clear that they could not be genuine errors at all.
As I wrote in my previous message, I already found the real problem, so my project is not compiling fine.