Skip to content

docs(@angular/cli): correct CSS resource output location in ng build description - #34383

Open
MeAkib wants to merge 1 commit into
angular:mainfrom
MeAkib:docs/build-media-output
Open

MeAkib wants to merge 1 commit into
angular:mainfrom
MeAkib:docs/build-media-output

Conversation

@MeAkib

@MeAkib MeAkib commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

The long description stated that resources referenced in CSS, such as images and fonts, are written and fingerprinted at the root of the output folder. The application builder writes them to the media directory of the browser output, which is configurable with outputPath.media, and only adds a hash when outputHashing is all or media.

…` description

The long description stated that resources referenced in CSS, such as images and
fonts, are written and fingerprinted at the root of the output folder. The
application builder writes them to the `media` directory of the browser output,
which is configurable with `outputPath.media`, and only adds a hash when
`outputHashing` is `all` or `media`.
@angular-robot angular-robot Bot added area: docs Related to the documentation area: @angular/cli labels Oct 18, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation in long-description.md for the build command. It clarifies that CSS resources, such as images and fonts, are written to the media directory of the browser output (configurable via outputPath.media) and fingerprinted when outputHashing is set to all or media, rather than being written directly to the root of the output folder. There are no review comments, and I have no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: @angular/cli area: docs Related to the documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant