{{ message }}
Repository navigation
Component update failed: Cannot read properties of undefined #29695
Description
Command
build
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
- ff
// typescript file
constructor(fbuserService: FbuserService) {
}
//===== the service
I get message when loading the component:
Component update failed: Cannot read properties of undefined
Minimal Reproduction
above read
Exception or Error
Component update failed: Cannot read properties of undefined
Your Environment
Angular CLI: 19.1.8
Node: 18.19.1
Package Manager: npm 10.2.4
OS: win32 x64
Angular: 19.1.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1901.8
@angular-devkit/build-angular 19.1.8
@angular-devkit/core 19.1.8
@angular-devkit/schematics 19.1.8
@angular/cdk 19.1.5
@angular/cli 19.1.8
@angular/fire 19.0.0
@angular/material 19.1.5
@schematics/angular 19.1.8
rxjs 7.8.1
typescript 5.6.3
zone.js 0.15.0
Anything else relevant?
No response
Activity
JeanMeche commentedon Feb 22, 2025
Hi, we'll need a reproduction to understand what's happening. Without it, this issue isn't actionnable to us.
fix(core): capture stack for HMR errors
fix(core): capture stack for HMR errors (#60067)
fix(core): capture stack for HMR errors (#60067)
fix(core): capture stack for HMR errors (#60067)
clydin commentedon Mar 3, 2025
If this is still occurring in your project, can you try updating to version 19.2?
This will at a minimum produce a more extensive error output which will help further investigation.
alan-agius4 commentedon Mar 7, 2025
Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.
angular-automatic-lock-bot commentedon Apr 7, 2025
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.