Announcing TypeScript 1.0.1

Announcing TypeScript 1.0.1

  • Comments 34

Today, we’re announcing the release of TypeScript 1.0.1. This release addresses user-reported issues around stability, performance, and Visual Studio 2012 compatibility. The upgrade is available as part of the Visual Studio 2013 Update 2, a Visual Studio 2012 power tool, npm package, and as source.

We’re also announcing the support plan for TypeScript going forward. We’re hard at work on new features, including many leveraging capabilities in upcoming versions of Visual Studio.  We will be moving our development efforts from Visual Studio 2012 to more recent releases, starting with Visual Studio 2013 Update 2. The TypeScript 1.0.1 release will be the final release supported on Visual Studio 2012. This will allow us to make the next TypeScript a more full-featured development experience in future releases.

Changelog:

Leave a Comment
  • Please add 1 and 2 and type the answer here:
  • Post
  • I suggest to consider not dropping VS2012 support, as most people I know still use it. This could be viewed negatively as a way to get everyone to upgrade, unless there's a better stated reason than the blanket "a more full-featured development experience". Just my 2 cents...

  • Great to see Typescript moving full steam ahead. Though I echo Jonathan's concerns. Dropping 2012 support does seem very sudden.

    Does this mean that VS2013 will share the same fate when 2014 is out?

  • I agree with the other comments about the drop in support for VS 2012 - I am forced to use VS2012 through my company and it is very unlikely that they'll agree to upgrade because one of my tools will not be supported.  It may force me and many in this same situation (I highly doubt I am the only one) to have to stop using it due to lack of support, which I really, really don't want to do.

  • While I use 2013, I would recommend MS fully support TypeScript on 2012 and up for at least the next 2 full versions. TypeScript is too new for MS to play the upgrade or die game with it. The community will see this very negatively, and may be cause for the MS haters to ignore TypeScript further.

  • While I'm not in the same boat as these others regarding the affect of dropping VS2012 support, I do have to agree on the possible negative impact this will have on TypeScript's continued adoption (and possible loss of existing developers who are locked into 2012). Considering companies rarely update on the "bleeding edge", it takes time for them to evaluate and upgrade.  By now, perhaps many companies are moving/have moved to VS2012, and suddenly now this wrench is thrown in - I'm guessing not a smart move at all.  I think if this decision is final, it should be delayed until at least a few months, or to the end of this year (to qualify as advanced warning).

  • Anyone noticed that it's 2014 now?

  • Thanks for the feedback on Visual Studio 2012 support for TypeScript.

    I want to confirm that you will be able to keep using TypeScript 1.0 in Visual Studio 2012, or you can download Visual Studio 2013 Express for free. And we plan to continue support for npm as well.

    We use your feedback to help us make decisions on our roadmap going forward, so please continue to share your thoughts and concerns with us.

    Polita

  • What doe mean 'Investigate async/await as a desugaring to ES6' on your roadmap ?

    It could be great to add async to ES3/5

  • @Tristan - With TypeScript, we are trying to keep to outputting clean JavaScript. Async/await needs to compile to state machines that tend to get pretty ugly, especially when you have to handle exceptions. With ES6, there will be generators, which will make async/await considerably cleaner to implement. That said, we will explore what is possible when we start investigating the feature.

  • Although it's great to see some momentum in Typescript community, I would *much* prefer effort be directed towards TS the language instead of seeing never-ending discussions about what version and what update of Visual Studio is or isn't going to be supported.

    There are other IDEs with decent TS support: WebStorm/IDEA or Eclipse, just to mention a few.

  • For some cases, elegancy of generated code may be important, but not for most cases. Many generated scripts are further minified. Best way is to implement two codepaths: one ugly way for ES3/5, and one for clean way with iterators for ES6. These different codepaths are probably unavoidable, because ES6 is huge improvement, and other TS features may require this. ES6 won't be adopted quickly and we need async now.

  • VS2012 people: you're going to have to upgrade at some point. The longer you leave it, the harder it gets. If I had £1500 for every day I've spent consulting with companies who have got themselves into a right mess by sticking with Visual Studio 2005 for years after its sell-by date... oh, wait. I do.

    Carry on. See you in five years.

    PS. My rate *will* have gone up by then.

  • Just throwing it out there with regards to ES5 support for generators: I really don't care about how ugly the output looks - that's what source maps are for. And besides, I have to support ES5 for at least another couple years, and the alternative to not having something like async/await results in code that is about as messy as the code you would have to generate anyway.

  • Will 1.0.1 also be the last release to support Notepad?  Sublime Text?  Vim?  Emacs?  WebStorm?  Eclipse?

    If so, you're planning to add WAY too much "magic" to TypeScript.  If not, it's pretty silly to cut off support for your own VS 2012 while keeping support for Notepad, Sublime Text, etc.  Biting the biggest hand that feeds you.

    My recommendation: keep existing VS2012 support in future versions of TypeScript, just don't try to "light up" the extra IDE magic for new features.

  • Is there any release notes on this version? Thanks!

Page 1 of 3 (34 items) 123