You can now use a DataStream 2 stream to deliver JavaScript logs to an external endpoint. You can also set the log-levels for the logs sent via DataStream 2.

You can now use subWorkers to make HTTP requests to EdgeWorkers on different properties or different accounts.

You can now configure an EdgeWorkers function to execute via an ESI (Edge Side Includes) fragment request on the enhanced TLS network.

You can now specify the severity of the logging messages included in the JavaScript logs. For more information go the log built-in module.

You no longer need to contact your Akamai representative to opt-in to this feature.

Flexible composition lets different development teams within an organization work separately to create and deploy multiple EdgeWorkers for the same website.

The getHeaders() method for the Request Object now supports all EdgeWorkers event handlers.

A built-in watermarking module is now available to use in your EdgeWorkers functions. You can use it to watermark Over-The-Top (OTT) content delivered in an Adaptive Bitrate (ABR) format. This watermarking solution currently doesn’t support interoperability with partial object caching. Please reach out to your account team if you require partial object caching.

You can now view EdgeWorkers error reports in the mPulse App Error List and App Error Summary dashboards. These reports include data about EdgeWorkers errors generated due to JavaScript errors. You can also find additional information in the form of a JavaScript stack trace. To learn more, go to the Integrate mPulse reports section in this guide.

The built-in crypto module now supports the sign() method that you can use to generate digital signatures.