Announcing TypeScript 1.0

Announcing TypeScript 1.0

Rate This
  • Comments 39

TypeScript 1.0

Today, we're happy to announce TypeScript 1.0. First, we want to give a big "thank you!" to everyone who has helped us over the last year and a half to meet this goal. Together, we've grown a language, tools, and a community around creating large-scale JavaScript applications. To help grow this community further, we're opening up TypeScript for contributions from the community starting today.
When we introduced Typescript to the world with our first release, TypeScript 0.8 in October 2012, we couldn't have imagined how the community would take shape.Our first release began with a small set of developers regularly interacting and sharing ideas. From there, it has become a thriving community of contributors, creating large projects and sharing hundreds of .d.ts files built from thousands of contributions.  Codebases written in TypeScript have been the TypeScript project’s proving ground, with some exceeding a half a million lines of code and continuing to grow in scale and complexity.  It’s time to cut the ribbon on TypeScript 1.0.
TypeScript 1.0 is available as part of Visual Studio 2013 and Visual Studio Web Express 2013 Spring Update, as an npm package, and as source. The TypeScript 1.0 release is also available as a power tool for Visual Studio 2012.

TypeScript is now a first-class citizen of Visual Studio, and we'll continue to invest in both the language and in making Visual Studio a more productive environment for JavaScript and TypeScript development, with Intellisense, project support, and powerful code navigation features. Community-contributed plugins for editors such as Eclipse also offer a seamless editing experience with statement completion, early errors, linting, and more.

Below, you can see examples of TypeScript in Visual Studio 2013 and Eclipse:

TypeScript in Visual Studio 2013

TypeScript in Eclipse

TypeScript 1.0 is a language designed with large-scale JavaScript application development in mind.  This offers a stable platform for users to build applications, and to create and share type definition files files that are compatible with future TypeScript versions.  TypeScript is also now a first-class citizen of Visual Studio, and we'll continue to invest in both the language and making Visual Studio a more productive environment for JavaScript and TypeScript development.

Taking Pull Requests

Today, we're announcing that we will begin taking pull requests for the TypeScript compiler and language service.
For now, we'll focus on fixing bugs, improving documentation, and general cleanup.  This will help us get the gears turning and work out any kinks in the submission process. This will be a learning process for us, and we will be open with the community throughout the process. Please be patient with us while we make the inevitable adjustments.  As we learn, we will continue to make TypeScript more open. We hope you'll be with us on this journey and contribute to the project.

How can I contribute?

Great question! You can contribute by submitting a bug fix pull request today. The steps are outlined on the TypeScript wiki.
We're excited about taking this step to make TypeScript even more open and even more of a collaboration between the TypeScript team and the TypeScript community.

Looking forward

Of course, our job isn't done. After we're done celebrating, we're getting back to work. The 1.0 release is just the beginning for TypeScript.
Thanks again for being part of this journey with us. We look forward to the road ahead! 

Leave a Comment
  • Please add 3 and 8 and type the answer here:
  • Post
  • I still have problem with compile on save, with just one particular file. This forces me to have to do it from the command line, I noticed that it does take a little while to build, but the end result is a perfect .js file with 0 errors. Does the UI have restrictions on compile time?

    And why does it still not properly nest the generated .js and file properly underneath the .ts file, and add it to the project? This makes my life a real pain to have to attach the file, then modify the .csproj file.

  • There is another free Eclipse IDE for TypeScript 1.0

  • It seems that the only reason why Typescript builds so slow is because it creates this seemingly useless dll in the bin folder. If you stick with compile on save, and rely on that, everything will compile much faster (you can toggle this in the TypeScript Build tab of the solution's properties).

    You can also turn off the build in Build > Configuration Manager, and uncheck the build checkboxes there. After doing that, the build solution option will only save all the files, and not build the dll file.

  • Microsoft haven't fixed one of javascript's weaknesses, they've obliterated one of its strengths!

  • @James Wilkins

    The 1.0 RTM release is largely a bugfix release of the 1.0 RC release.  


    We don't have built-in unit test tools yet, but some people use unit testers like tsunit and chutzpah with TypeScript.

    @Felipe Fujiy

    You'll need to update to Visual Studio 2013 Update 2 rather than staying on Update 1 to get TypeScript 1.0.  We're becoming a supported in-box language of Visual Studio.

  • @Kevin

    Can you share the file that's giving you problems on the TypeScript issue tracker?  This would help us track down what might be causing the problem.

    For .js and nesting: for TypeScript you could think of these as .exe and .pdb files.  You wouldn't put them in the project alongside your source files, but they are still deployed.  The same is true with TypeScript.  We'll deploy the .js as part of the build, but think of the .js files as output rather than input.

  • Yay! Kudos toTS team!

  • The only thing I want now is the ability to declare explicit "define" module names for require js within typescript... I am loving this release so far.

  • With version 1.0, I no longer have the option in VS2013 to refactor > rename... Just wondering if that was intentional, or if there's a way to get it back? Thanks.

  • @Antiriad 680x0

    What version of Visual Studio?  Visual Studio Professional 2013 and above should support refactor->rename with TypeScript 1.0.

  • I was able to get the file to build. It seems like the issue was related to the .csproj file. It had been used since the earliest release, and overtime the format seems to have changed. I went through a massive clean up, including removing all .js and files from the project and source control, TFS does seem to be building it once the update was applied to the build server, and not deploying the .ts file.

    So far, 1.0 is perfect. Good job team!

  • Great new scripting language, what's the status on the integration with Azure's PaasS?

  • I created a TypeScript community on Google+

  • Hello,

    Are there any guidelines/best practices/coding conventions available for TypeScript? If yes, please share the document/link where they can be accessed.

  • @Vlad Avram

    You can use TypeScript anywhere you were using JavaScript before.  


    There are no official code conventions for TypeScript.  TypeScript is a superset of JavaScript, so one possible route would be to use code conventions that your team uses for JavaScript.

Page 2 of 3 (39 items) 123