Microsoft puts its spin on JavaScript with TypeScript(techrepublic.com)
techrepublic.com
Microsoft puts its spin on JavaScript with TypeScript
http://www.techrepublic.com/blog/programming-and-development/microsoft-puts-its-spin-on-javascript-with-typescript/6943
2 comments
I cannot recomment WebStorm enough. Has great support for Type/JavaScript and IntelliSense works automatically from sources for the runtime/libraries you are using.
Have tough time getting used to definition files at the moment. Microsoft only offers a v0.8.8 file of Node.js. Loads floating on GitHub that contain errors. Not good. I suspect it is one of those thing where until a lot of people use TypeScript and there are defs for different versions of libraries (by authors), it will be a bit of a wild west.
Have tough time getting used to definition files at the moment. Microsoft only offers a v0.8.8 file of Node.js. Loads floating on GitHub that contain errors. Not good. I suspect it is one of those thing where until a lot of people use TypeScript and there are defs for different versions of libraries (by authors), it will be a bit of a wild west.
I can relate to the unstableness of the TypeScript intellisense for VS2012, although Web Essentials 2012 does improve things.
However, I easily trade the unstableness of intellisense for the type-safety of TypeScript.
However, I easily trade the unstableness of intellisense for the type-safety of TypeScript.
Has anyone used TypeScript in conjunction with Node.js? I love developing in the Node ecosystem, but the lack of type checking is irritating.
I haven't worked with Node myself, but you can find a definition file here: https://github.com/borisyankov/DefinitelyTyped/tree/master/n...
Fly at it, I say.
Fly at it, I say.
Yes. Microsoft offers a Node.js v0.8.8 definition file in their examples. There are some others floating on Github for other versions.
I use WebStorm to give me autocomplete for the version of Node I am running. The defs are there just to make the compiler shut up.
I use WebStorm to give me autocomplete for the version of Node I am running. The defs are there just to make the compiler shut up.
The only thing I would complain about is some of the tooling is still a bit unstable, which is understandable. I'm using Visual Studio 2012.
I've been looking forward to 0.9 for some time now, as the generic support allows me to fully express all of the types in my system.
To me the most beautiful thing about TypeScript is it's compatibility with JavaScript and how definition files work. Definition files essentially allow you to write code contracts against existing pieces of JavaScript code that may or may not be outside of your control.
https://github.com/borisyankov/DefinitelyTyped is a good resource for definition files.