func new httpTrigger seems to have wrong parameter order

[lobunto]

The handler-function arguments for httpTrigger functions seem to be in the wrong order when creating a new httpTrigger function.

When I run the func new command (locally in a terminal) and select httpTrigger as the function type, a file with this content is generated:

const { app } = require('@azure/functions');

app.http('httpTrigger', {
  methods: ['GET', 'POST'],
  authLevel: 'anonymous',
  handler: async (request, context) => {
    context.log(`Http function processed request for url "${request.url}"`);

    const name = request.query.get('name') || (await request.text()) || 'world';

    return { body: `Hello, ${name}!` };
  },
});

If I run the function with func start, the function throws this error to the console and gives me a 500 error in the browser:

After changing the order of the arguments from the handler function to have context first and request as second (handler: async (context, request)), my function works as expected.

Is this a known issue?

[ejizba]

The template is correct. My guess is you are on an old version of the npm package. Can you make sure you're on @azure/functions v4.0.0-alpha.9 or greater?

More info:

• https://learn.microsoft.com/en-us/azure/azure-functions/functions-node-upgrade-v4?tabs=azure-cli-set-indexing-flag%2Cv4#switch-the-order-of-arguments
• InvocationContext should be second parameter to HTTP trigger function azure-functions-nodejs-library#34

[anddoutoi]

I just created a new function project by running:

func init api --worker-runtime node --language javascript --model V4

The package.json created looks like this:

{
  "name": "",
  "version": "1.0.0",
  "description": "",
  "main": "src/functions/*.js",
  "scripts": {
    "start": "func start",
    "test": "echo \"No tests yet...\""
  },
  "dependencies": {
    "@azure/functions": "^4.0.0-alpha.1"
  },
  "devDependencies": {
    "azure-functions-core-tools": "^4.x"
  }
}

and @azure/[email protected] is installed.

Using this preset and creating a function by running:

cd api

followed by:

func new --name "my-endpoint" --template "HTTP trigger"

creates a "legacy" handler with the wrong signature.

TL;DR: The dependency ^4.0.0-alpha.1 should probably be updated to the latest to avoid differences between JS and TS function projects.