Repository navigation
Change default dist folder to "browser" #190
Description
With the new application builder (introduced in Angular 17), the build artifacts are placed in a "browser" subfolder. This is why we made the "dir" option for the deployment builder.
When using the application builder, it is mandatory to set "dir".
As soon as the application builder is the only officially supported builder (i.e. as soon as the Webpack-based builder is deprecated), we should change the default path so that the application builder works out of the box without "dir".
Activity
JohannesHoppe commentedon May 28, 2024
If I remember correctly, this is only an issue for the standalone version. When using
ng deploythe correct folder is chosen by default.JohannesHoppe commentedon Dec 30, 2025
With ng deploy this has always worked - we read outputPath from angular.json and build the correct path. With #200 we improved this further to handle all Angular versions from 18-21 correctly. For the standalone CLI we'd need some kind of discovery (parsing angular.json ourselves), and honestly if you're using the CLI directly you'll probably need to fiddle with --dir anyway depending on your setup. I'd say wontfix for the standalone CLI.
JohannesHoppe commentedon Jan 12, 2026
Update: This is now fixed in v3.0.0 for
ng deploy! 🎉The builder automatically appends
/browserto the output path, so Angular 17+ projects work out of the box without setting--dir.For the standalone CLI version (
npx angular-cli-ghpages), this remains a wontfix – you'll need to specify the path manually.