TypeScript Roadmap

TypeScript today is an early preview. We welcome
your discussions of the language specification (docx,
pdf). Here are a few themes we are currently considering for the TypeScript compiler and language services.

Improve the TypeScript type system's ability to express API intent.

Continue to align with ECMAScript 6 where there are shared capabilities, as that standard evolves.

Comments

I strongly recommend that next TS version has a high speed incremental compilation mode. eg. "-quick" can allow developers to quickly compile file without the strict check when they only have small changes in code. It can save a lot of time.

Typescript changes everything. As an asp.net developer that makes me feel really good that microsoft is putting some effort into what could become a game changer for the whole industry.Keep the momentum guys! On my wish list is to see more integrations to serialize/deserialize easily between c# and typescript. How cool would it be to have type safety between client and server!

Wow, just discovered about typescript and I am completely amazed. Started using it right away. It makes it so easier to maintain the code now that we have features like strong typing, classes, interfaces and generics.

Some features I would love to see on the road map:

- C# like properties with getters and setters. Would be extremely useful when using with MV* frameworks.

I like TypeScript, it is a beautiful language. I also like the VS integration. Is there a timeline for the roadmap? I would love to see where the roadmap is going with regards to web server side development such as Node.js, or if the development team has plans to implement other solutions.

Waiting for the project reaching to the final production quality.Great to know now that the project is evolving and not dead as the upshot project.Can not find something comparable among the other open source projects.So, the waiting is the only option.

@jonturner: thanks for the info. So we'll have to wait for 0.9.x before modules will get comfortable. Will that include loaders, and do you have a rought idea of the timescale?I appreciate the need to focus development, but I had somehow hoped that TS might take on the role of general ESS6 transpiler. Are there longer-term plans to integrate other ES6 features, like destructuring, proxies, generators, or will you wait for engine implementations to provide these?Oh, will your async/await be based on generators?

Would the 'community site' include integration with package management? I would like to see some level of integration with npm or nuget so that .d.ts files are associated with specific versions of packages.

@clausreinke: the ES6 alignment means that we'll being trying to align with at least the class and module syntax (and likely lambda syntax). There may be other things as well, but definitely planning alignment at least for the ES6 features we already support.

Thanks for starting a real roadmap! (btw, though I'm subscribed to the project feeds, I only got notified of the comment, not the page update)I would strongly suggest to give the ES6 module system details priority at least equal to generics. Given the project's goals, it is sad that the TS compiler is written using an include system, instead of module import/export. That demonstrates that the module support is not sufficient yet, and users are running into the limitations.Could you be more specific about the 'align' in 0.9.x, please? Which features?