TypeScript 1.3 protected error TypeScript 1.3 protected error typescript typescript

TypeScript 1.3 protected error


thank you all guys. for your answers!the reason was (oh, what's the shame =) ) the ReSharper.It's validation was showing that error, suspending it i'm getting no errors now.Looks like JetBrains guys should update their definitions like Web Essentials did.As they aren't compatible with new TS version, 1.3. And no updates pending as for now.

Hope, it'll be useful for somebody else.


The answer to your question then is ReSharper 9.0 EAP.It supports TypeScript 1.3 features: 'protected' modifier and tuples.You're welcome to try it. Though, yes, it's a pre-release version, so overall stability is not strictly guaranteed.


Are you building from within Visual Studio, or from the command-line? What with different versions of the SDK being installed, as well as potentially the NPM package globally (if you've ever installed that), it can get quite messy as to which version gets picked up. For example, if I run 'where tsc' from the command prompt, I get the below hits (and this is without the 1.1 SDK on the path, though I am in the bin folder for testing the latest bits)

S:\src\TypeScript\bin>where tscS:\src\TypeScript\bin\tscS:\src\TypeScript\bin\tsc.jsC:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\tsc.exeC:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\tsc.jsC:\Users\billti\AppData\Roaming\npm\tscC:\Users\billti\AppData\Roaming\npm\tsc.cmd

Can you verify via "where tsc" the locations and order you PATH is resolving the 'tsc' command?

That said, if you're building from within a VS project, it should locate the latest SDK via the build target. Does this also occur with a new TypeScript project (where the latest version and targets file should be referenced)?

Failing that, and I hate to say it... ready... did you try rebooting? :-) Sometimes updates to the PATH etc.. after an install don't get picked up until processes restart, and things like MSBuild can actually linger waiting for the next build as a perf optimization, rather than exit once the build is done (and thus may not pick up environment changes immediately).