This project is read-only.

TypeScript 0.9.1

Rating:        Based on 21 ratings
Reviewed:  20 reviews
Downloads: 0
Change Set: 85e121b750a4
Released: Aug 6, 2013
Updated: Aug 6, 2013 by jonturner
Dev status: Alpha Help Icon

Available Downloads

There are no downloads associated with this release.

Release Notes

The following TypeScript 0.9.1 releases are available: To download a zip file of the source for this release, click the change set id, and then click Download.

You can also read more about this release in the blog post.

Reviews for this release

Memory leaks in VS is off the charts, it seems to just get worse and worse the newer version you use
by Fresa on Aug 22, 2013 at 2:39 PM
Love the new features, perf is slightly better in large TS projects but... syntax error highlighting is flakey, there are tonnes of misleading and seemingly random compiler error messages that come and go, the compiler allows invalid JS to be output and the latest Web Essentials tooling fails to compile if you are outputting to AMD modules. This release is unfortunately a bust.
by RWHepburn on Aug 21, 2013 at 12:05 AM
I'm trying to use this release for a fairly large project but it's hard, some compiler errors that just do not make sense.
by prgjonas on Aug 20, 2013 at 10:47 PM
I'm very sorry to say that this release has broken a very large project that was working fine in 0.8.3. Objects have become un-newable for some reason, compiler also reporting that one of the project files is not a supported encoding?! Love Typescript, but I've had to roll back to the earlier release.
by nwoodhouse on Aug 20, 2013 at 11:01 AM
terrible version,many error in large projects and an unstable environment dont use it
by Natikr on Aug 19, 2013 at 2:47 PM
The compiler consumes a gig of RAM in 10 seconds. Sadly, I'll stay with 0.8.3 until things are worked out.
by web2nr on Aug 14, 2013 at 5:37 PM
While the concept of the changes are good, this is not a good release. The handling of 'this' is unstable, getting generic compiler errors (Unable to get value of the property 'flags': object is null or undefined), and compile on save. It's unusable for me
by kevinsbennett on Aug 13, 2013 at 6:38 PM
memory leaking visual studio. unusable.
by mickdelaney on Aug 12, 2013 at 6:05 PM
Looks like most of the performance issues have been resolved and a few bugs fixed as well.
by Quango on Aug 12, 2013 at 2:40 PM
VS2012 express for web, error when compile a new project: unsupported locale:"zh_CN". ActivityLog: 未能正确加载TypeScriptLanguageService.VsPackage.LanguageServicePackage包。
by zhangqizhi on Aug 12, 2013 at 8:46 AM
Bad release. After few minutes tones of console and tsc ghost process, please add a new release quickly.
by freier on Aug 11, 2013 at 7:11 PM
Changing my review too. The workaround is working!
by danfma on Aug 11, 2013 at 6:14 PM
Horrible memory leaks.
by stijnherreman on Aug 9, 2013 at 1:31 PM
Changing my review from one star. Updated all .d.ts files and the fix from has my project compiling in seconds. Big thanks to the team for looking into what is a problem for the linq team. Keep up the good work!!
by jcutrono on Aug 9, 2013 at 2:04 AM
I love typescript but this is killing me! My status windows have said (refreshing...) for the last 15 minutes and I can't debug for than a few steps without locking up the IDE. Please fix this soon. Returning to plain javascript is unthinkable but this hurts.
by ca0v on Aug 8, 2013 at 2:50 PM
Yes, this release has serious memory problems, but don't write it off just yet. It appears most of us were using particularly complex generics and there is a regression. If you're using linqjs, (linq.d.ts) then check out the workaround here:
by oisin on Aug 7, 2013 at 6:09 PM
In my case, this version works really well. It solved all the performance issues that I was experiencing with the unusable v0.9.0.*. +50 .ts in the project. I'm using VS 2013 without extensions. I don't use the Generics feature at this moment.
by Rigel77 on Aug 7, 2013 at 6:55 AM
Scrolling down the errors list will cause VS2012 to stop responding, 1 CPU pegged at 100% I have disabled all plugins ( ie WebEssentials ) and I still get the same problem. Not ready
by rslaney on Aug 7, 2013 at 2:29 AM
I think this release needs to be rolled back. It chews up horrible amounts of RAM until it crashes Visual Studio. Steer clear of this one, folks.
by smithkl42 on Aug 6, 2013 at 10:49 PM
I hate to do this as I love TypeScript, but this release is not ready for primetime. Visual Studio now consumes memory out of control until ultimately crashing, something it didn't do with The quality control REALLY needs to be improved before you drop these releases.
by MgSam on Aug 6, 2013 at 10:25 PM