dev-server keeps stale code of a linked (`file:`) library after `ng-packagr --watch` rebuilds it (rebuild reported, restart required)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 48/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- angular, node.js, typescript
- Bereich
- build-system, devtools
Rechercherichtung
Start with the linked reproduction and inspect how ng serve resolves and caches the linked library’s libreria.mjs while its source map changes. Compare the resolved file path and rebuilt bundle after ng-packagr --watch updates the library. Done means the app bundle contains and runs the new code without restarting ng serve.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Command
serve
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
In a workspace with an application and a separate Angular library linked with a file: dependency, rebuilding the library in watch mode makes ng serve print "Application bundle generation complete", but the application bundle (main.js) still contains the previous compiled code of the library. The new code only appears after stopping and restarting ng serve.
The source map embedded in the same main.js already contains the new library source (sourcesContent), while the code is the old one. So the updated .map file seems to be re-read, but the content of libreria.mjs is reused from a previous build.
I could not determine whether this is the in-memory load cache, the file watcher, or something else.
Minimal Reproduction
Setup
-
Windows, project and library in sibling folders (
D:\...\proyecto-22andD:\...\libreria-22). -
Library built with
ng build libreria --watch --configuration development(ng-packagr). -
App
package.json:"libreria": "file:../libreria-22/dist/libreria"(npminstall-links=false, sonode_modules/libreriais a Junction tolibreria-22\dist\libreria). -
preserveSymlinksis not set (enabling it is not an option for me: the library sources then resolve under the app's folder and breakpoints in the library do not bind in VS Code). -
angular.jsonof the app:"build": { "configurations": { "development": { "optimization": false, "extractLicenses": false, "sourceMap": { "scripts": true, "styles": true, "vendor": true } } } }, "serve": { "options": { "poll": 1000, "prebundle": { "exclude": ["libreria"] } } } -
Angular CLI cache enabled (default).
Steps to reproduce
- Create the app and a library (
ng new,ng generate library libreria), and build the library once intodist/libreria. - In the app, add
"libreria": "file:../libreria-22/dist/libreria"and runnpm install. - In the library, create a service with a method containing
console.log('v1'), and call it from the app's root component. - Run
ng build libreria --watch --configuration developmentin the library, andng servein the app. - Change the log in the library service to
console.log('v2')and wait until ng-packagr finishes.
Expected: the dev-server rebuilds and the app runs v2.
Actual: the terminal prints "Application bundle generation complete" but the app still runs v1. Searching main.js shows the old code:
// ../libreria-22/dist/libreria/fesm2022/libreria.mjs
...
console.log("v1"); // old code
while the embedded source map has the new source:
sourcesContent: "... console.log('v2'); ..."
dist/libreria/fesm2022/libreria.mjs on disk does contain the new code. Stopping and restarting ng serve fixes it.
Things I tried without success
poll: 1000inserve.options(with restart).- Deleting
.angular/cacheand restarting (works until the next library change). prebundle.excludewith the package name.- Starting from a shell with the drive letter in uppercase (
D:) instead of lowercase. <remove this line if you did not launchng servefrom that shell>
Minimum Reproduction
https://github.com/LuisEscamillaMartin/repro-linked-lib-stale
Exception or Error
No error. The build reports success.
Your Environment
Angular CLI : 22.2.5
Node.js : 24.21.0
Package Manager : npm 11.19.0
Operating System : win32 x64
Anything else relevant?
Without preserveSymlinks, the library is bundled into main.js from its real path (../libreria-22/dist/libreria/fesm2022/libreria.mjs), outside node_modules.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 27k
- Forks
- 11.8k
- Ø Merge
- 1 T. 2 Std.
- Gemergte PRs (30 T.)
- 225
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
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
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Offenarea: @angular/build
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
angular/angular-cli#34764 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayEvtl. vergeben @0z5a hat das heute übernommen. Offenarea: @schematics/angular
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
angular/angular-cli#34761 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 72/100
angular/angular-cli#34760 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Evtl. vergeben @SkyZeroZx hat das vor 1 Tag übernommen. Offenarea: @angular/ssr
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 20/100
angular/angular-cli#34754 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: @schematics/angular
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 74/100
angular/angular-cli#34730 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in angular/angular-cli
Ähnliche Issues
-
status/need-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
google-gemini/gemini-cli#30384 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
P2
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug ready-for-human
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue priority: low size: XS
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
vercel-labs/scriptc#3979 ·
Maintainer antworten meist innerhalb von 1 Tag