0.13.0

Features

• API endpoints can now return a Fetch Response (e.g. return fetch('https://domain.com/resource') or return new Response('...'). This enables using the API as a proxy. The main way to return data is still using serializable objects such as return { data: { value: true } }.
• Props requests during SPA are now more intelligent. If a handler for the current route is not found in the filesystem (<root>/functions/props/routeName.js), the request will be skipped. Previously, you had to provide route.meta.propsGetter: false manually to skip requests but this is not needed anymore.
• Added CORS utilities (see docs).

Fixes

• Worker types.

Breaking changes

• When deploying to Node environments (e.g. Vercel), the request passed to the backend handlers (API and Props) is now a Fetch Request to make it similar to the development environment. The original Node's request is provided as rawRequest. --- CFW deployments are not affected.