dev-server keeps stale code of a linked (`file:`) library after `ng-packagr --watch` rebuilds it (rebuild reported, restart required)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- angular, node.js, typescript
- Área
- build-system, devtools
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 27k
- Forks
- 11.8k
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 225
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de angular/angular-cli
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Abiertoarea: @angular/build
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
angular/angular-cli#34764 ·
Los mantenedores suelen responder en 1 día
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap arrayPosiblemente ocupada @0z5a la tomó hoy. Abiertoarea: @schematics/angular
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
angular/angular-cli#34761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
angular/angular-cli#34760 ·
Los mantenedores suelen responder en 1 día
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)Posiblemente ocupada @SkyZeroZx la tomó hace 1 día. Abiertoarea: @angular/ssr
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
angular/angular-cli#34754 ·
Los mantenedores suelen responder en 1 día
-
area: @schematics/angular
Dificultad 3/5 1-2 días Aptitud para principiantes 74/100
angular/angular-cli#34730 ·
Los mantenedores suelen responder en 1 día
Todos los issues de angular/angular-cli
Issues similares
-
status/need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
google-gemini/gemini-cli#30384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
P2
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
bug ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
LucasSantana-Dev/Lucky#3150 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue priority: low size: XS
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vercel-labs/scriptc#3979 ·
Los mantenedores suelen responder en 1 día