Migrate Actions from to Node.js 16 to Node.js 18
As part of our mission to support every future version of LTS Node.js through Actions and to be in line with the Node JS developer community, we are releasing Node 18 while Node 16 is still in Active LTS. We urge all cusomters to transition today to Node 18 and make the most of its LTS. Remember, while Node 16 LTS remains available until September, their use may involve certain risks following the conclusion of LTS and we recommend you to update to Node 18.
Node.js 18 is now generally available (GA) across our entire suite of extensibility offerings. This includes Actions, Rules, Hooks, Database Scripts, and Custom Social Connections. We strongly encourage everyone to update to Node 18 by Sept 11, 2023, to adhere to best code security practices.
|Node 16/12||Update to Node 18 by Sept 11, 2023||To use new Node 18, create new Actions with Node 18 or update existing Actions by creating and deploying a new version.|
|Node 18 Beta in Actions||Update to Node 18 by Sept 11, 2023.||To switch to Node 18 GA, simply update existing Actions by creating and deploying a new version.|
|Oracle||Stop using it.||Remove service.|
|Node.js C#||Stop using it.||Remove service.|
||Make sure all node modules are added as dependencies on the Actions that use them.||Add as dependencies on the Actions that use them.|
|Miscellaneous system binaries or programs||Stop using them.||Remove binaries because most of them will become unavailable.|
|Filesystem write access||Stop writing files to
Move to Actions
Actions is designed to support multiple versions of Node concurrently, and now supports Node 12, Node 16, and Node 18. In addition, no-code Actions integrations follow industry-standard "always current" version control with minor versions updated automatically. The underlying code remains current to the latest LTS Node.js. We encourage all customers move to Actions.
These task are only required if you want to use the Node 18 version.
Create new Actions with Node 18
Customers can start using Node 18 by creating new Actions with Node 18:
Navigate to Actions > Library, and select Build Custom.
For Runtime, select
Write your custom Actions in Node 18, test, and deploy when ready.
Choose Node 18 for other extensibility products
Update other extensibility products in Auth0 Dashboard.
Navigate to Dashboard > Settings > Advanced.
Scroll down to Extensibility.
For Runtime, select
Upgrade existing Actions
Existing Actions built on Node 16 can be upgraded to Node 18 and later reverted to a previous version on Node 16 if needed. Upgrade Actions to Node 18 by creating and deploying a new version set to use Node 18 as the runtime.
Migrate Rules and Hooks to Actions
Wherever possible, migrate Rules and Hooks to Actions. To determine which Rules and Hooks can be migrated, read Actions Limitations. To learn how to migrate your Rules and Hooks to Actions, see our guides available at Migrate to Actions.
While there should be no significant breaking changes as a part of the Actions Node 18, please follow our recommendations for using Node 18.