dev-server keeps stale code of a linked (`file:`) library after `ng-packagr --watch` rebuilds it (rebuild reported, restart required)

未关闭
#34,728 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃

调研方向

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 内容生成。

描述

area: @angular/build
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-22 and D:\...\libreria-22).

  • Library built with ng build libreria --watch --configuration development (ng-packagr).

  • App package.json: "libreria": "file:../libreria-22/dist/libreria" (npm install-links=false, so node_modules/libreria is a Junction to libreria-22\dist\libreria).

  • preserveSymlinks is 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.json of 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

  1. Create the app and a library (ng new, ng generate library libreria), and build the library once into dist/libreria.
  2. In the app, add "libreria": "file:../libreria-22/dist/libreria" and run npm install.
  3. In the library, create a service with a method containing console.log('v1'), and call it from the app's root component.
  4. Run ng build libreria --watch --configuration development in the library, and ng serve in the app.
  5. 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: 1000 in serve.options (with restart).
  • Deleting .angular/cache and restarting (works until the next library change).
  • prebundle.exclude with the package name.
  • Starting from a shell with the drive letter in uppercase (D:) instead of lowercase. <remove this line if you did not launch ng serve from 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

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。