ERROR in Cannot read property '0' of undefined after upgrade to Angular 10

I'm having the same issue. I tracked down the stack trace by running ng serve in the vs code debugger and having it break on unhandled errors.

For me the error is:

Exception has occurred: TypeError: Cannot read property '0' of undefined
  at Object.typeToValue (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/reflection/src/type_to_value.js:45:66)
    at /workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/reflection/src/typescript.js:75:58
    at Array.map (<anonymous>)
    at TypeScriptReflectionHost.getConstructorParameters (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/reflection/src/typescript.js:57:36)
    at Object.getConstructorDependencies (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/annotations/src/util.js:29:36)
    at extractInjectableCtorDeps (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/annotations/src/injectable.js:232:72)
    at InjectableDecoratorHandler.analyze (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/annotations/src/injectable.js:72:31)
    at TraitCompiler.analyzeTrait (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:346:40)
    at analyze (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:298:58)
    at _loop_1 (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:320:21)
    at TraitCompiler.analyzeClass (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:326:35)
    at visit (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:108:27)
    at visitNodes (/workingcopypath//node_modules/typescript/lib/typescript.js:18956:30)
    at Object.forEachChild (/workingcopypath//node_modules/typescript/lib/typescript.js:19189:24)
    at visit (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:110:20)
    at TraitCompiler.analyze (/workingcopypath//node_modules/@angular/compiler-cli/src/ngtsc/transform/src/compilation.js:112:13)

The failing code in question is this line:

return noValueDeclaration(typeNode, decl.declarations[0]); 

I'm still looking for the fix, but at least this should help debug the issue.

You can do this using this .vscode/launch.json

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Debug Ng Serve",
      "skipFiles": ["<node_internals>/**"],
      "cwd": "${workspaceFolder}",
      "program": "./node_modules/.bin/ng",
      "args": ["serve", "--verbose=true"]
    }
  ]
}

I had this error too. I was missing to add all the packages I used in my code in the package.json depencencies (in my case ng-bootstrap), after this the error vanished.

It's all about wrong imports. You are trying to import the files that does not exist or their location is different :)

I also spent a few minutes checking the issue and the simple ng lint was definitely not throw me to missing or failed imports, but when executing the ng lint with various flags like this:

ng lint --force=true --typeCheck=true

I found other things that helped me get to the error.

I had to go into each Page/Component and Module to check one by one.

Toggle all the VS Code folders and checking the "Problems" tab of the VS Code and thus right the imports.

This happened to me replicating one project to another and removing unused references and so on.

Since Angular didn't manage to provide a meaningful error description, let's ask TypeScript compiler for it. In my case it worked like a charm, showing the exact place and reason:

tsc --project <path-to-your-project>/tsconfig.json

Pay attention, in case of several tsconfig's, use the one intended to build your application, it might be tsconfig.app.json whatever. You can find it out under the options.tsConfig section of angular.json.

Run the build in dev mode. ng build and it points the error at the exact place.

Not sure if you have already fixed this problem, but I've solved it by updating Angular (and it's dependencies) into 10.1.2

Here's what I have actually.

dependencies": {
"@angular/animations": "~10.1.2",
"@angular/cdk": "^10.2.2",
"@angular/common": "~10.1.2",
"@angular/compiler": "~10.1.2",
"@angular/core": "~10.1.2",
"@angular/forms": "~10.1.2",
"@angular/material": "^10.2.2",
"@angular/platform-browser": "~10.1.2",
"@angular/platform-browser-dynamic": "~10.1.2",
"@angular/router": "~10.1.2",
"rxjs": "~6.5.5",
"tslib": "^2.0.0",
"zone.js": "~0.10.  
},

"devDependencies": {
    "@angular-devkit/build-angular": "~0.1000.2",
    "@angular/cli": "~10.0.2",
    "@angular/compiler-cli": "~10.1.3",
    "@types/angular": "^1.7.3",
    "@types/jasmine": "~3.5.0",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.5.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~3.3.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~3.9.5"
  }

I got this error every time a ran ng build or ng serve after a big merge. The only way that worked for me was by 'divide and conquer'. I have moved to a new (test) branch and isolated/deleted all new modules/components/files that have come from merge and after every change I ran ng build. When the error disappeared, I did undo previously deleted files and isolated smaller and smaller chunks until I got to the source of error. For me it was a wrong import path.

Virendra Singh Rathore is right

It's all about wrong imports. Your are trying to import the files that do not exist or their location is different :)

In my situation, the error appeared after transferring classes to another file. VS code didn't show the error location. I had to open all the files and look for corrupted 'imports'.

I had the same error after updating from Angular 9 to 10.

The problem was solved for me after updating dev dependencies:

npm update --save-dev 

In my Case -->

import { AppModule } from './app/app.module';  //main.ts file
import { ApicallService } from 'src/app/services/apicall.service'; //In a component file

These are are the reasons that showing me ERROR in Cannot read property '0' of undefined Error. So I solved it with changing the paths.

import { AppModule } from './app/app/app.module'; //main.ts file
import { ApicallService } from 'src/app/app/services/apicall.service';

We had the same issue. After trying everything from this list, we updated all the dependencies and the message which was given was more descriptive. It was one import path that wasn't set correctly that caused the issue.

In my case it's very basic one. when I'm trying to "service" in my "component", i imported like

import  SetPasswordService  from './set-password.service';

But after checking each line, I added "curly braces" it's gone.

import { SetPasswordService } from './set-password.service';