{"id":1647,"date":"2019-02-25T00:00:00","date_gmt":"2019-02-25T08:00:00","guid":{"rendered":""},"modified":"2025-06-17T01:58:26","modified_gmt":"2025-06-17T08:58:26","slug":"improving-the-typescript-support-in-azure-functions","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/improving-the-typescript-support-in-azure-functions\/","title":{"rendered":"Improving the TypeScript support in Azure Functions"},"content":{"rendered":"\n

TypeScript is becoming increasingly popular in the JavaScript community. Since Azure Functions runs Node.js, and TypeScript compiles to JavaScript, motivated users already could get TypeScript code up and running in Azure Functions. However, the experience wasn\u2019t seamless, and things like our default folder structure made getting started a bit tricky. Today we\u2019re pleased to announce a set of tooling improvements that improve this situation. Azure Functions users can now easily develop with TypeScript when building their event-driven applications!<\/p>\n\n\n\n

For those unfamiliar, TypeScript is a superset of JavaScript which provides optional static typing, classes, and interfaces. These features allow you to catch bugs earlier in the development process, leading to more robust software engineering. TypeScript also indirectly enables you to leverage modern JavaScript syntax, since TypeScript is compatible with ECMAScript 2015.<\/p>\n\n\n\n

With this set of changes to the Azure Functions Core Tools and the Azure Functions Extension for Visual Studio Code, Azure Functions now supports TypeScript out of the box! Included with these changes are a set of templates for TypeScript, type definitions, and npm scripts. Read on to learn more details about the new experience.<\/p>\n\n\n\n

Templates for TypeScript<\/h2>\n\n\n\n

In the latest version of the Azure Functions Core Tools<\/a> and the Azure Functions Extension for VS Code<\/a>, you\u2019re given the option to use TypeScript when creating functions. To be more precise, on creation of a new function app, you will now see the option to specify TypeScript on language stack selection. This action will opt you into default package.json and .tsconfig files, setting up their app to be TypeScript compatible. After this, when creating a function, you will be able to select from a number of TypeScript specific function templates. Each template represents one possible trigger, and there is an equivalent present in TypeScript for each template supported in JavaScript.<\/p>\n\n\n\n

\"Select<\/a><\/figure>\n\n\n\n

The best part of this new flow is that to transpile and run TypeScript functions, you don\u2019t have to take any actions at all that are unique to Functions. For example, what this means is that when a user hits F5 to start debugging Visual Studio Code, Code will automatically run the required installation tasks, transpile the TypeScript code, and start the Azure Functions host. This local development experience is best in class, and is exactly how a user would start debugging any other app in VS Code.<\/p>\n\n\n\n

Learn more about how to get your TypeScript functions up and running in our documentation<\/a>.<\/p>\n\n\n\n

Type definitions for Azure Functions<\/h3>\n\n\n\n

The @azure\/functions<\/a> package on npm contains type definitions for Azure Functions. Have you ever wondered what\u2019s an Azure Function object is shaped like? Or maybe, the context object that is passed into every JavaScript function? This package helps! To get the most of TypeScript, this should to be imported in every .ts function. JavaScript purists can benefit too \u2013 including this package in your code gives you a richer Intellisense experience. Check out the @azure\/functions<\/a> package on npm to learn more!<\/p>\n\n\n\n

Npm scripts<\/h3>\n\n\n\n

Included by default in the TypeScript function apps is a package.json file including a few simple npm scripts. These scripts allow Azure Functions to fit directly into your typical development flow by calling specific Azure Functions Core Tools commands. For instance, \u2018npm start\u2019 will automatically run \u2018func start\u2019, meaning that after creating a function app you don\u2019t have to treat it differently than any other Node.js project.<\/p>\n\n\n\n

To see these in action, check out our example repo<\/a>!<\/p>\n\n\n\n

Try it yourself!<\/h2>\n\n\n\n

With either the Azure Functions Core Tools<\/a> or the Azure Functions Extension for VS Code<\/a>, you can try out the improved experience for TypeScript in Azure Functions on your local machine, even if you don\u2019t have an Azure account.<\/p>\n\n\n\n

Next steps<\/h3>\n\n\n\n