• support for Angular 17 (no support for earlier versions) --> support for various buildTargets (similar to angularfire) and recognises different output path configurations (see feat(@angular-devkit/build-angular): allow customization of output locations angular/angular-cli#26675 and [es-build] Browser directory created in outputPath angular/angular-cli#26304 (comment))
• completely removes the --no-silent option, error messages will be shown by default now (modern CI systems don't expose secrets anymore)
• adds --dir option, this overrides the directory for all published sources, relative to the current working directory. The normal logic with buildTargets and conventions is ignored in this case.
• adds --no-notfound option to not create a 404.html which should work great with Cloudflare pages, see Github Pages: Configuration to avoid initial 404 Network Response #178 and see https://developers.cloudflare.com/pages/configuration/serving-pages/#single-page-application-spa-rendering
• adds a .nojekyll file by default, can be disabled via --no-nojekyll
• updated deps (hint: commander + ghpages are still the same version, because this would require much more testing and removals of workarounds)
• removes husky + prettier, because the setup broke and I won't miss them
• removes circle-ci build

Install via

ng add [email protected]

FYI Cloudflare docs: Single-page application (SPA) rendering

If your project does not include a top-level 404.html file, Pages assumes that you are deploying a single-page application. This includes frameworks like React, Vue, and Angular. Pages’ default single-page application behavior matches all incoming paths to the root (/), allowing you to capture URLs like /about or /help and respond to them from within your SPA.