The new EdgeWorkers Postman collection (beta) is now available! Try the API, build workflows, and stay on top of development changes.

• You can now use the EdgeWorkers Code Profiler to gain insight about the memory usage consumed by your EdgeWorkers code.

• The EdgeWorkers API and CLI now support a JSON Web Token (JWT) to use for authentication when adding enhanced debug headers to your requests or profiling your code.

• To tell the browser to delete a cookie immediately, you can now set the maxAge to zero.

• The maximum streaming request size is currently 16 KB when request.body is called in the responseProvider event handler. We'll increase this limit to its previous value of 1 MB in the near future.

• You can now set default properties for the config commands in the EdgeWorkers CLI. To learn more, see Provide Default Config Properties.

The Request Object now includes the arrayBuffer() method. It returns a promise that resolves to an arrayBuffer containing the bytes of the request.

You can now use onOriginResponse and onOriginRequest to dynamically build a response from your JavaScript code using the respondWith method.

We've updated the EdgeWorkers built-in reports to provide more information to help you optimize the performance and stability of your EdgeWorkers functions. You can use the EdgeWorkers Management application or the API to view these reports.

You can now use the following User Location Object properties to specify the geographic location of a request:

The EdgeWorker Code Profiler now supports the IntelliJ Plugin.

If you've saved a draft of an EdgeWorker version you can now open it in the diff tool of the code bundle editor.

We updated the following limits in the Dynamic Compute resource tier.

We've made the following updates to the code bundle editor and the encoding module: