Skip to content

Releases: Azure/azure-functions-nodejs-worker

Azure Functions Node.js Worker 3.5.2

15 Nov 19:25
7f2afaa

Choose a tag to compare

  • Updated @azure/functions to version 3.5.0-alpha.5 (#644)
  • Allowed Node.js v19 to be used in local development environments (#645)
  • Enabled the new programming model to work in the multiple concurrent worker scenario (#638)

NOTE: This version of the worker was included with v4.15 of the host which finished rolling out in February 2023.

Azure Functions Node.js Worker 3.5.1

04 Oct 22:00
abf81b9

Choose a tag to compare

Fixed

  • App failed to start with error "Worker was unable to load entry point" #630

NOTE: This version of the worker was included with v4.14 of the host which finished rolling out in December 2022.

Azure Functions Node.js Worker 3.5.0

26 Aug 17:24
d0340c9

Choose a tag to compare

Added

  • Support for entry point app-level code #537
  • Property to access the request body as a buffer (bufferBody) #294
  • Support for app start and terminate hooks #539
  • Preview support for the new programming model ✨🥳. More information here: http://aka.ms/AzFuncNodeV4

Fixed

  • Bug where nested "bytes" property causes invocation to fail #607
  • Bug where environment variable casing was not always maintained on Windows #600

Changed

  • Created a separate NPM package to contain most of the Node.js framework for Azure Functions. Now you can get updates faster (or slower 😅) by including the npm package directly in your app instead of waiting for a rollout in Azure! More details here

NOTE: This version of the worker originally rolled out with v4.12.0 of the host, but was reverted in v4.12.2. Changes will be included in v3.5.1 of the worker.

Azure Functions Node.js Worker 3.4.0

14 Jun 00:44
bbfc4ab

Choose a tag to compare

  • Added initial support for Node 18. IMPORTANT: This is only one piece of the puzzle and is not intended as an official announcement for Azure Functions as a whole. Follow #562 for more details and announcements
  • Added feature to help detect blocking synchronous code. Disabled by default because it negatively impacts performance. Use AZURE_FUNCTIONS_NODE_BLOCK_LOG to turn it on #558

Azure Functions Node.js Worker 3.3.0

08 Apr 23:07
6be9f0d

Choose a tag to compare

  • Added support for pre and post invocation hooks (#522)

Azure Functions Node.js Worker 3.2.0

23 Mar 20:43
6ad4bfe

Choose a tag to compare

  • Added a parseFormBody method to the HttpRequest that can be used to parse content of type "x-www-form-urlencoded" and "multipart/form-data" (#347)
  • Respect package.json "type" field when deciding if functions should be loaded as ESM or CommonJS (#531)

Type Definitions 3.2.0

23 May 22:31
6ad4bfe

Choose a tag to compare

Added

  • Added a parseFormBody method to the HttpRequest that can be used to parse content of type "x-www-form-urlencoded" and "multipart/form-data" (#347)
  • Add interface for HTTP Response (#169)

Changed

  • Add deprecation flag for context.done. We have no plans to remove this method at this time, however we strongly recommend using async/await instead (#549)

Azure Functions Node.js Worker 2.1.3

16 Feb 00:40
5052bb3

Choose a tag to compare

  • Added debug-level logs to improve supportability in the following cases:
    • Worker received invocation request (#355)
    • Detected missing "package.json" file, which may affect cold start (#449)

Azure Functions Node.js Worker 3.1.0

09 Feb 18:57
9557399

Choose a tag to compare

  • Added a user property to the HttpRequest that contains an object representing the logged in user (#421)
  • Allow Node.js v17.x and v15.x to be used during local development (These versions are not officially supported) (#363)
  • Added debug-level logs to improve supportability in the following cases:
    • Worker received invocation request (#355)
    • Detected missing "package.json" file, which may affect cold start (#449)

Type Definitions 3.1.0

23 May 21:51
9557399

Choose a tag to compare

  • Added a user property to the HttpRequest that contains an object representing the logged in user (#421)