{"id":401,"date":"2015-06-05T10:00:00","date_gmt":"2015-06-05T10:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/typescript\/2015\/06\/05\/developing-in-typescript-on-a-mac-with-sublime\/"},"modified":"2019-02-20T10:46:13","modified_gmt":"2019-02-20T17:46:13","slug":"developing-in-typescript-on-a-mac-with-sublime","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/developing-in-typescript-on-a-mac-with-sublime\/","title":{"rendered":"Developing in TypeScript on a Mac with Sublime"},"content":{"rendered":"

Within the TypeScript team, many of us have Macs that we use for development. We’ve also heard from some of you that you’d like to use your OS X machines to build TypeScript projects. So recently, we’ve been focusing on building a natural and rich developer toolset for Mac and Linux fans.<\/span><\/p>\n

Starting with TypeScript 1.5, TypeScript projects have complete tooling support in OS X using Sublime<\/a>, Atom<\/a>, and Visual Studio Code<\/a>.<\/p>\n

In this article, we’ll be talking about how to set up your Mac for developing TypeScript using Sublime.<\/span><\/p>\n

Getting started<\/span><\/h2>\n

First, install the TypeScript compiler, which you can get via <\/span>npm<\/span><\/a>.  You can install this once you have node by installing the ‘typescript’ package.  Since this installs globally, we run the command using ‘sudo’:<\/span><\/p>\n

> sudo npm install -g typescript<\/span><\/p>\n

Next, we’ll add the TypeScript support for Sublime.  The TypeScript package is available via <\/span>Package Control<\/span><\/a>.  Once you have Package Control installed, you can search for the TypeScript package.  First, bring up the command palette with Cmd+Shift+P.<\/span><\/p>\n

\"Screen<\/span><\/p>\n

Next, select Package Control: Install Package and search for ‘typescript’.  You’ll see there are a few packages that match ‘typescript’, but the one we want is simply ‘TypeScript’.<\/p>\n

\"Screen<\/p>\n

After you’ve installed the ‘TypeScript’ package, you’ll be able to begin working with TypeScript projects.  You can do a quick test to make sure everything is working by starting up a new TypeScript (*.ts) file.  Let’s make a hello.ts:<\/p>\n

\/\/ hello.ts<\/span>
function<\/span> greet(msg: string<\/span>) {<\/span>
  console.log(msg);<\/span>
}<\/p>\n

greet(42);<\/span><\/p>\n

Notice that Sublime will help you as you type in the example, giving auto-complete help as you dot into console and argument help as you begin the call into log.<\/p>\n

\"Screen<\/p>\n

TypeScript also warns us against passing a number when we intended to pass a string by squiggling under the number and changing the status at the bottom of the editor when we click on the squiggled text.  This is pretty helpful for finding simple bugs before we deploy our project.<\/p>\n

\"Screen<\/p>\n

Now that we’re set up Sublime to work with TypeScript, the next thing we want to do is to create a TypeScript project.  Starting with 1.5, TypeScript supports a lightweight project file called ‘tsconfig.json’.  We can write a tsconfig.json for our hello app:<\/p>\n

\"Screen<\/p>\n

The ‘tsconfig.json’ file has two main parts: the options passed to the compiler and the list of files.  In the example, I switch on source maps, so the TypeScript compiler will generate a .map file we can use to directly debug the TypeScript rather than the generated JavaScript.  I also list the files explicitly to show how you can control which files are included in the build.  For this example, this step is optional.  If you leave off the “files” section, ‘tsconfig.json’ will compile all *.ts files in the same directory.<\/span><\/p>\n

We have all we need to build the app now.  We can open a terminal, cd to our project directory, and run the compiler with the ‘tsc’ command.<\/p>\n

\"Screen<\/p>\n

Oh right!  We forgot to fix the issue in ‘hello.ts’.  Let’s update hello.ts to pass in a string instead:<\/p>\n

\/\/ revised hello.ts<\/span><\/p>\n

function<\/span> greet(msg: string<\/span>) {
<\/span> console.log(msg);
<\/span>}<\/span><\/p>\n

greet(“Greetings, OS X”<\/span>);<\/span><\/p>\n

Now, when we re-run the build, the error goes away.  We can also run our file using node.<\/p>\n

\"Screen<\/p>\n

Debugging our app<\/span><\/h2>\n

If we look at our project directory, we’ll see the output JavaScript as well as the source map file we enabled earlier:<\/p>\n

\"Screen<\/p>\n

Let’s use the source map file so we can debug our TypeScript source.  To do so, we’ll create a small html page that will call our hello.js:<\/p>\n

\"Screen<\/p>\n

Next, we’ll open up Chrome and our index.html.  Opening the Developer Tools in Chrome via Option+Cmd+I or through the “More tools” menu, we can see the same output we saw running the app in the terminal earlier:<\/p>\n

\"Screen<\/p>\n

We can also work with the TypeScript we created by clicking on the “hello.ts:2” link to the right or switching to the Sources tab.  Notice how Chrome uses the source map file to map from the hello.js file back to the original hello.ts.<\/p>\n

\"Screen<\/p>\n

What’s next<\/h2>\n

We’re just getting warmed up.  There are a lot of resources to help you get going.  You can browse the <\/span>TypeScript handbook<\/a> to learn TypeScript, ask the team and the TypeScript community questions via <\/span>StackOverflow<\/a> and the <\/span>TypeScript GitHub<\/a> site, and start working with a variety of JavaScript libraries by adding their <\/span>type information<\/a> to your project.  If you’re using TypeScript on a Mac and have some suggestions for how we can make the experience better, we’d <\/span>love to hear them<\/a>!<\/span><\/p>\n


<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Within the TypeScript team, many of us have Macs that we use for development. We’ve also heard from some of you that you’d like to use your OS X machines to build TypeScript projects. So recently, we’ve been focusing on building a natural and rich developer toolset for Mac and Linux fans. Starting with TypeScript […]<\/p>\n","protected":false},"author":377,"featured_media":1797,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-401","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-typescript"],"acf":[],"blog_post_summary":"

Within the TypeScript team, many of us have Macs that we use for development. We’ve also heard from some of you that you’d like to use your OS X machines to build TypeScript projects. So recently, we’ve been focusing on building a natural and rich developer toolset for Mac and Linux fans. Starting with TypeScript […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/401","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/users\/377"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/comments?post=401"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/401\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media\/1797"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media?parent=401"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/categories?post=401"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/tags?post=401"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}