In this guide, you will create a newAngular ↗ application and deploy to Cloudflare Workers (with the newWorkers Assets).

Use thecreate-cloudflare ↗ CLI (C3) to set up a new project. C3 will create a new project directory, initiate Angular's official setup tool, and provide the option to deploy instantly.

To usecreate-cloudflare to create a new Angular project with Workers Assets, run the following command:

npmcreatecloudflare@latest--my-angular-app--framework=angular

yarncreatecloudflaremy-angular-app--framework=angular

pnpmcreatecloudflare@latestmy-angular-app--framework=angular

After setting up your project, change your directory by running the following command:

cdmy-angular-app

After you have created your project, run the following command in the project directory to start a local server. This will allow you to preview your project locally during development.

npmrunstart

yarnrunstart

pnpmrunstart

Your project can be deployed to a*.workers.dev subdomain or aCustom Domain, from your own machine or from any CI/CD system, includingCloudflare's own.

The following command will build and deploy your project. If you're using CI, ensure you update your"deploy command" configuration appropriately.

npmrundeploy

yarnrundeploy

pnpmrundeploy

By default, Cloudflare first tries to match a request path against a static asset path, which is based on the file structure of the uploaded asset directory. This is either the directory specified byassets.directory in your Wrangler config or, in the case of theCloudflare Vite plugin, the output directory of the client build. Failing that, we invoke a Worker if one is present. If there is no Worker, or the Worker then uses the asset binding, Cloudflare will fallback to the behaviour set bynot_found_handling.

Refer to therouting documentation for more information about how routing works with static assets, and how to customize this behavior.