Skip to content

Commit b02a6fa

Browse files
authored
fix up TS also
1 parent c4b2439 commit b02a6fa

File tree

1 file changed

+11
-28
lines changed

1 file changed

+11
-28
lines changed

articles/azure-functions/create-first-function-cli-typescript.md

Lines changed: 11 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create a TypeScript function from the command line - Azure Functions
33
description: Learn how to create a TypeScript function from the command line, then publish the local project to serverless hosting in Azure Functions.
4-
ms.date: 03/06/2023
4+
ms.date: 12/15/2023
55
ms.topic: quickstart
66
ms.devlang: typescript
77
ms.custom: devx-track-azurecli, devx-track-azurepowershell, mode-other, devx-track-js
@@ -50,27 +50,20 @@ Before you begin, you must have the following prerequisites:
5050
In Azure Functions, a function project is a container for one or more individual functions that each responds to a specific trigger. All functions in a project share the same local and hosting configurations. In this section, you create a function project that contains a single function.
5151

5252
::: zone pivot="nodejs-model-v3"
53-
1. Run the `func init` command, as follows, to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:
53+
In a suitable folder, run the [`func init`](functions-core-tools-reference.md#func-init) command, as follows, to create a TypeScript Node.js v3 project in the current folder:
5454

5555
```console
56-
func init LocalFunctionProj --typescript
56+
func init --typescript --model V3
5757
```
58-
59-
2. Navigate into the project folder:
60-
61-
```console
62-
cd LocalFunctionProj
63-
```
64-
65-
This folder contains various files for the project, including configurations files named [local.settings.json](functions-develop-local.md#local-settings-file) and [host.json](functions-host-json.md). Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
58+
This folder now contains various files for the project, including configurations files named [local.settings.json](functions-develop-local.md#local-settings-file) and [host.json](functions-host-json.md). Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
6659

6760
3. Add a function to your project by using the following command, where the `--name` argument is the unique name of your function (HttpExample) and the `--template` argument specifies the function's trigger (HTTP).
6861

6962
```console
7063
func new --name HttpExample --template "HTTP trigger" --authlevel "anonymous"
7164
```
7265

73-
`func new` creates a subfolder matching the function name that contains a code file appropriate to the project's chosen language and a configuration file named *function.json*.
66+
[`func new`](functions-core-tools-reference.md#func-new) creates a subfolder matching the function name that contains a code file appropriate to the project's chosen language and a configuration file named *function.json*.
7467

7568
### (Optional) Examine the file contents
7669

@@ -95,31 +88,21 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
9588
::: zone-end
9689

9790
::: zone pivot="nodejs-model-v4"
98-
1. Run the `func init` command, as follows, to create a functions project in a folder named *LocalFunctionProj* with the V4 programming model:
99-
100-
```console
101-
func init LocalFunctionProj --model V4
102-
```
103-
104-
You're then prompted to choose a worker runtime and a language - choose Node for the first and TypeScript for the second.
105-
106-
2. Navigate into the project folder:
91+
1. In a suitable folder, run the [`func init`](functions-core-tools-reference.md#func-init) command, as follows, to create a TypeScript Node.js v4 project in the current folder:
10792

10893
```console
109-
cd LocalFunctionProj
94+
func init --typescript
11095
```
11196

112-
This folder contains various files for the project, including configurations files named *local.settings.json* and *host.json*. Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
97+
This folder now contains various files for the project, including configurations files named *local.settings.json* and *host.json*. Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file. Required npm packages are also installed in *node_modules*.
11398

114-
3. Add a function to your project by using the following command:
99+
1. Add a function to your project by using the following command, where the `--name` argument is the unique name of your function (HttpExample) and the `--template` argument specifies the function's trigger (HTTP).
115100

116101
```console
117-
func new
102+
func new --name HttpExample --template "HTTP trigger" --authlevel "anonymous"
118103
```
119104

120-
Choose the template for "HTTP trigger". You can keep the default name (*httpTrigger*) or give it a new name (*HttpExample*). Your function name must be unique, or you're asked to confirm if your intention is to replace an existing function.
121-
122-
You can find the function you added in the *src/functions* directory.
105+
[`func new`](functions-core-tools-reference.md#func-new) creates a file named *HttpExample.ts* in the *src/functions* directory, which contains your function's code.
123106

124107
4. Add Azure Storage connection information in *local.settings.json*.
125108
```json

0 commit comments

Comments
 (0)