library builder: in watch mode, editing a Sass partial doesn't re-emit components that import it via @use
@alan-agius4 is already working on this.
Since Sep 18, 2026.
Assessment
This issue has not been assessed yet.
Description
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 --watchthen change mixin torgb(2,2,2);- rebuild logs success, FESM still has
#010101. Touching widget.ts flushes it and#020202appears
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.
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 176
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from angular/angular-cli
-
area: @angular/build gemini-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
angular/angular-cli#33055 · 1 comment · 3 reactions ·
-
area: @angular/build gemini-triaged
Difficulty 4/5 3-5 days Newbie friendliness 72/100
angular/angular-cli#34137 ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 assignee ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 assignee ·
All issues in angular/angular-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·