Angular 18新构建系统迁移后出现bindingStartIndex读取错误

问题描述 #

将作为应用依赖的自定义库项目从Angular 17升级到Angular 18，执行了以下更新命令：

npm i typescript@5.5.4
ng update @angular/core@18 ng update @angular/cli@18 
ng update @angular-eslint/schematics@18 ng update @angular/material@18

升级完成后运行应用，浏览器控制台抛出如下错误：

main.ts:10 ERROR TypeError: Cannot read properties of null (reading 'bindingStartIndex')
    at ɵɵelementStart (core.mjs:23501:53)
    at AppComponent2_Template (template.html:1:1)
    at executeTemplate (core.mjs:11788:5)
    at renderView (core.mjs:12950:7)
    at renderComponent (core.mjs:12896:3)
    at renderChildComponents (core.mjs:12996:5)
    at renderView (core.mjs:12978:7)
    at ComponentFactory.create (core.mjs:16260:9)
    at _ApplicationRef.bootstrap (core.mjs:31811:38)
    at core.mjs:33216:56

项目通过本地tgz包引入自定义组件库：

"@mylib/dashboards": "file:../MyLib.Dashboards/dist/dashboards/mylib-dashboards-18.0.0.tgz"

已尝试的操作：

• 在tsconfig.json中添加Angular库路径映射，试图解决依赖冲突
• 在angular.json的build配置中启用preserveSymlinks: true，无效果

移除@angular/*路径配置后，错误消失，但实现InMemoryDbService的Mock数据服务无法加载。项目完整package.json如下：

{
  "name": "widgets-app",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "jest --coverage --verbose --silent",
    "lint": "ng lint",
    "build_prod": "ng build widgets --configuration production",
    "pack": "cd dist/widgets && npm pack",
    "package": "npm run build_prod && npm run pack",
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^18.2.7",
    "@angular/cdk": "^18.2.7",
    "@angular/common": "^18.2.7",
    "@angular/compiler": "^18.2.7",
    "@angular/core": "^18.2.7",
    "@angular/forms": "^18.2.7",
    "@angular/material": "^18.2.7",
    "@angular/material-moment-adapter": "^18.2.7",
    "@angular/platform-browser": "^18.2.7",
    "@angular/platform-browser-dynamic": "^18.2.7",
    "@angular/router": "^18.2.7",
    "@asymmetrik/ngx-leaflet": "^18.0.1",
    "@mylib/dashboards": "file:../MyLib.Dashboards/dist/dashboards/mylib-dashboards-18.0.0.tgz",
    "@mylib/layout": "^18.0.2",
    "@ngx-translate/core": "^15.0.0",
    "@ngx-translate/http-loader": "^8.0.0",
    "@syncfusion/ej2-angular-pivotview": "^27.1.48",
    "angular-in-memory-web-api": "0.18.0",
    "echarts": "^5.4.3",
    "leaflet": "^1.9.4",
    "leaflet.markercluster": "^1.5.3",
    "moment": "^2.29.4",
    "ng-dynamic-component": "^10.7.0",
    "ngx-daterangepicker-material": "^6.0.4",
    "ngx-echarts": "^18.0.0",
    "ngx-skeleton-loader": "^9.0.0",
    "ngx-translate-multi-http-loader": "^18.1.0",
    "rxjs": "^7.8.1",
    "uuid": "^9.0.0",
    "zone.js": "~0.14.10"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^18.2.7",
    "@angular-eslint/builder": "^18.3.1",
    "@angular-eslint/eslint-plugin": "^18.3.1",
    "@angular-eslint/eslint-plugin-template": "^18.3.1",
    "@angular-eslint/schematics": "^18.3.1",
    "@angular-eslint/template-parser": "^18.3.1",
    "@angular/cli": "^18.2.7",
    "@angular/compiler-cli": "^18.2.7",
    "@ngneat/spectator": "^19.0.0",
    "@types/jest": "^29.5.13",
    "@types/leaflet": "^1.9.12",
    "@typescript-eslint/eslint-plugin": "^8.6.0",
    "@typescript-eslint/parser": "^8.6.0",
    "eslint": "^9.12.0",
    "eslint-config-prettier": "^9.1.0",
    "eslint-plugin-prettier": "^5.2.1",
    "jest": "^29.7.0",
    "jest-auto-spies": "^3.0.0",
    "jest-preset-angular": "^14.2.4",
    "jest-sonar": "^0.2.16",
    "ng-mocks": "^14.13.1",
    "ng-packagr": "^18.2.1",
    "prettier": "^3.3.3",
    "typescript": "~5.5.4"
  }
}

解决步骤 #

1. 对齐本地库与主应用的Angular版本 #

本地库@mylib/dashboards当前版本为18.0.0，而主应用使用18.2.7，版本不一致会导致核心库重复加载，引发运行时错误：

• 升级本地库的所有Angular依赖到^18.2.7
• 重新构建库，生成新的tgz包，更新主应用中该库的引用路径

2. 完善路径映射配置 #

保留tsconfig.json中的@angular/*路径映射，同时补充angular-in-memory-web-api的路径配置，解决Mock数据加载问题：

"paths": {
  "@angular/*": [
    "node_modules/@angular/*"
  ],
  "angular-in-memory-web-api": [
    "node_modules/angular-in-memory-web-api"
  ]
}

3. 检查本地库的构建配置 #

确保本地库的ng-package.json正确配置peerDependencies，避免打包时嵌入Angular核心代码：

"peerDependencies": {
  "@angular/core": "^18.0.0",
  "@angular/common": "^18.0.0"
  // 添加其他必要的peer依赖
}

同时启用strictMetadataEmit，保证组件元数据正确生成：

"lib": {
  "strictMetadataEmit": true
}

4. 清理缓存并重装依赖 #

执行以下命令彻底清除缓存，避免旧版本代码残留：

rm -rf node_modules package-lock.json
npm cache clean --force
npm install

同时删除本地库的dist目录，重新构建生成最新的包文件。

内容的提问来源于stack exchange，提问作者Ihescode