library builder: in watch mode, editing a Sass partial doesn't re-emit components that import it via @use

Offen

#34,124 erstellt am 18.9.2026 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@alan-agius4 arbeitet bereits daran.

Seit 18.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

angular/build:library area: @angular/build gemini-triaged

Command

build

Is this a regression?

Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Found while tesing #34106 cc @alan-agius4

In --watch changing a partial that component stylesheet reaches through @use logs a successful rebuild, but component's CSS in FESM stays old. Editing component's own .scss or .html works (what watch_spec covers)

Non watch builds are fine

Minimal Reproduction

widget.scss: @use './styles/shared' as s; .my-widget { @include s.paint; };
_shared.scss: @mixin paint { color: rgb(1,1,1); }
ng build mylib --watch then change mixin to rgb(2,2,2);
rebuild logs success, FESM still has #010101. Touching widget.ts flushes it and #020202 appears

Exception or Error

Your Environment

@angular/build built from #34106 (e1fa5796) with the repo's own bazel build

Angular CLI 22.1.8, 
Angular 22.1.7, 
Node 24.16.0, 
pnpm 11, 
macOS 25.6, 
14 cores, 
24 GB

Anything else relevant?

sass itself is re-bundled correctly. component never enters affectedFiles because only the direct styleUrl is a known resource dependency. application builder expands modified files with FileReferenceTracker (compiler-plugin.ts); the library pipeline doesn't use it.

On ngwr every component stylesheet @uses the theme partials, so any token or mixin edit in watch is stale.

Vorherrschende Sprache: TypeScript
Sterne: 27k
Forks: 11.8k
Ø Merge: 16 Std. 21 Min.
Gemergte PRs (30 T.): 170

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus angular/angular-cli

Can't use an array of hostnames in --allowedHosts cli parameter in @angular/build:dev-server Offen

area: @angular/build gemini-triaged

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100

angular/angular-cli#33955 · Erstellt am 28.8.2026
Allow tests to pass without any test files (e.g. via Vitest `passWithNoTests`) Offen

area: @angular/cli gemini-triaged

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100

angular/angular-cli#33055 · 1 Kommentar · 3 Reaktionen · Erstellt am 26.4.2026
library builder: tslib is not added to the output package.json Offen

angular/build:library area: @angular/build gemini-triaged

angular/angular-cli#34131 · 1 zugewiesene Person · Erstellt am 20.9.2026
library builder: a name re-exported through two "export *" paths is dropped from the bundle Offen

angular/build:library area: @angular/build gemini-triaged

angular/angular-cli#34130 · 1 zugewiesene Person · Erstellt am 20.9.2026
library builder: entry points a/b and a-b are built into the same bundle Offen

angular/build:library area: @angular/build gemini-triaged

angular/angular-cli#34128 · 1 zugewiesene Person · Erstellt am 19.9.2026

Alle Issues in angular/angular-cli