Skip to content

fix(@schematics/angular): remove explicit index option from new applications #30192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

clydin
Copy link
Member

@clydin clydin commented Apr 28, 2025

With the index option now defaulting to <project_source_root>/index.html for the application build system, the explicit value present in new applications is no longer required. This removal further reduces the size of the angular.json file for new projects.

@clydin clydin added the target: major This PR is targeted for the next major release label Apr 28, 2025
@clydin clydin force-pushed the ng-new/default-index branch 2 times, most recently from 35077d3 to ad5d672 Compare April 29, 2025 00:15
clydin added 2 commits April 28, 2025 20:36
…cations

With the index option now defaulting to `<project_source_root>/index.html`
for the `application` build system, the explicit value present in new
applications is no longer required. This removal further reduces the size
of the `angular.json` file for new projects.
The `@angular/pwa` add schematic now attempts to discover a default index
option value if a configuration usage path within the build target is
possible. The default value as per the `application` build system is
`<project_source_root>/index.html`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant