You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
library builder: in watch mode, editing a Sass partial doesn't re-emit components that import it via @use #34124
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.
@alan-agius4 re-tested on 5579d742: still reproduces. On ngwr, editing a mixin in theme/styles/_mixins.scss during --watch recompiles 5 entry points, but their FESM still has the old CSS; a clean non-watch build with the same edit picks it up.
Activity
thekhegay commentedon Sep 18, 2026
@alan-agius4 re-tested on
5579d742: still reproduces. On ngwr, editing a mixin in theme/styles/_mixins.scss during --watch recompiles 5 entry points, but their FESM still has the old CSS; a clean non-watch build with the same edit picks it up.thekhegay commentedon Sep 28, 2026
@alan-agius4 looks like fixed in f62445c,
runWatchLoopkeepsinvalidate()result now. Closing