dev-server keeps stale code of a linked (`file:`) library after `ng-packagr --watch` rebuilds it (rebuild reported, restart required)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- angular, node.js, typescript
- 领域
- build-system, devtools
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- TypeScript
- 星标
- 27k
- 派生
- 11.8k
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 225
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
angular/angular-cli 的其他 Issue
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)未关闭area: @angular/build
难度 2/5 1-3 小时 新手友好度 65/100
angular/angular-cli#34764 ·
维护者通常 1 天内回复
-
ng add @angular/ssr fails with TypeError when an NgModule in the app module file has no bootstrap array可能已有人在做 @0z5a 今天认领。 未关闭area: @schematics/angular
难度 2/5 1-3 小时 新手友好度 90/100
angular/angular-cli#34761 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
angular/angular-cli#34760 ·
维护者通常 1 天内回复
-
Angular SSR can crash `AngularAppEngine` servers with a single aborted request (22.2.6 regression)可能已有人在做 @SkyZeroZx 于 1 天前认领。 未关闭area: @angular/ssr
难度 4/5 3-5 天 新手友好度 20/100
angular/angular-cli#34754 ·
维护者通常 1 天内回复
-
area: @schematics/angular
难度 3/5 1-2 天 新手友好度 74/100
angular/angular-cli#34730 ·
维护者通常 1 天内回复
查看 angular/angular-cli 的全部 Issue
相似的 Issue
-
status/need-triage
难度 2/5 1-3 小时 新手友好度 76/100
google-gemini/gemini-cli#30384 · 1 条评论 ·
维护者通常 1 天内回复
-
P2
难度 1/5 1 小时以内 新手友好度 84/100
维护者通常 1 天内回复
-
bug ready-for-human
难度 2/5 1-3 小时 新手友好度 60/100
LucasSantana-Dev/Lucky#3150 ·
维护者通常 1 天内回复
-
enhancement good first issue priority: low size: XS
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
vercel-labs/scriptc#3979 ·
维护者通常 1 天内回复