Skip to content

Commit 2b11d94

Browse files
committed
last feedback
1 parent b65a0fe commit 2b11d94

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/functions-node-upgrade-v4.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Version 4 of the Node.js programming model requires the following minimum versio
3131

3232
## Include the npm package
3333

34-
For the first time, the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package contains the primary source code that backs the Node.js programming model for Azure Functions. Previously, that code shipped directly in Azure and the npm package only had the TypeScript types. Moving forward both JavaScript and TypeScript users need to include this package in their app. v3 apps _can_ include the npm package, but it isn't required.
34+
For the first time, the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package contains the primary source code that backs the Node.js programming model. In previous versions, that code shipped directly in Azure and the npm package only had the TypeScript types. Moving forward, you need to include this package for both TypeScript and JavaScript apps. You _can_ include the package for existing v3 apps, but it isn't required.
3535

3636
> [!TIP]
3737
> Make sure the `@azure/functions` package is listed in the `dependencies` section (not `devDependencies`) of your `package.json` file. You can install v4 with the command
@@ -184,7 +184,7 @@ context.res = {
184184
context.done(null, {
185185
body: `Hello, ${name}!`
186186
});
187-
// Option 3:
187+
// Option 3, but you can't use this option with any async code:
188188
context.res.send(`Hello, ${name}!`);
189189
// Option 4, if "name" in "function.json" is "res":
190190
context.bindings.res = {

0 commit comments

Comments
 (0)