TypeScript 0.9.5 beta

You can get the beta for the upcoming 0.9.5 release here. This release is focused on memory usage, reliability, and better spec conformance. We'd like to get your feedback on how the beta works for your project before we release 0.9.5.

Note: please read the breaking change notices as there have been breaking changes between 0.9.1.1 and 0.9.5 that may affect your code.

Last edited Nov 18, 2013 at 4:48 PM by jonturner, version 10

Comments

cwmacdon Nov 27, 2013 at 6:34 PM 
Is there any chance you could include the "Add TypeScript File" so that we don't have to manually change the BuildAction property of all new files?

jonturner Nov 27, 2013 at 3:17 PM 
@cwmacdon - I believe the IE10 restriction was only temporary and that we're planning to remove it. We're locking down for 0.9.5, so the change to lift the restriction would likely come later.

@csnover - That came from the general tightening of type checking rules. After we switched the default type inference from 'any' to '{}', people were accidentally leaving off type arguments and getting into trouble where type errors were appearing much later and they couldn't figure out why. It's a little bit more verbose, but the hope is that the intent in the code is clearer.

csnover Nov 26, 2013 at 4:21 PM 
Noting in 0.9.5 beta that attempting to use Array as a type results in “TS2173: Generic type references must include all type arguments.” and must be replaced with e.g. “any[]”. Did not see this in the breaking changes notes; intentional?

cwmacdon Nov 26, 2013 at 4:01 PM 
Is there a reason it requires IE10?

oisin Nov 26, 2013 at 2:12 PM 
@alexdresdo - Sounds like a perfect reason for you to do it and submit a pull request with fixes. That's what makes the world go around ;)

novaleaf Nov 20, 2013 at 11:43 PM 
@johnturner: ok yes that makes sense. for some reason I thought you couldn't do that in 0.9.1.1 either.

jonturner Nov 20, 2013 at 5:28 PM 
@novaleaf - the nesting is for external modules. If you have an external modules, we no longer allow you to 'declare' additional external modules inside of that, as external modules should be rooted at the global namespace. Sorry for the confusion, perhaps the breaking change notice needs some rewording.

novaleaf Nov 20, 2013 at 11:13 AM 
or i think there's a LKG folder in the source too...

novaleaf Nov 20, 2013 at 11:12 AM 
@nintendud: you can also install the beta and copy the tsc.js found under C:\Program Files (x86)\Microsoft SDKs\TypeScript\0.9

novaleaf Nov 20, 2013 at 11:10 AM 
i just fixed the errors on my main .ts files, and seems like i can still nest external modules no problem, so I guess I just don't understand the "no nested modules" feature change...

novaleaf Nov 19, 2013 at 11:53 PM 
The "no nested modules" breaking change: why do this? it seems like this is a huge breaking change and impacts architecture. Is it really true that now you can only "namespace" 1 level deep? and the only half-workaround is static properties of a class? (that only gets you 1 level deeper, with added confusion of looking like the class is instantiable)

please tell me i'm missing something.....

jonturner Nov 18, 2013 at 7:59 PM 
@nintendud - We'll make the NPM available for the official 0.9.5 release. For now, the best way is to build out of source.

nintendud Nov 18, 2013 at 6:09 PM 
Can we get the NPM module separate from the installer for those on non-Windows platforms?

Thanks!

alexdresko Nov 18, 2013 at 5:01 PM 
I SO want to do this.. I just know that there will be a handful of DefinitelyTyped definitions I'm using aren't going work after the upgrade. :)