I'm encountering a similar issue, and I managed to trace the stack trace by utilizing the VS Code debugger and setting breakpoints on unhandled errors.

The error I am facing 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 code that is causing the failure is located in this line:

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

I am still in the process of finding a solution, but this information should aid in troubleshooting the problem.

You can achieve this by updating your .vscode/launch.json file as follows:

{
  // 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"]
    }
  ]
}

Dealing with a similar issue, I also encountered this error. It turned out that the solution was to ensure all packages utilized in my code were included in the package.json dependencies list - such as 'ng-bootstrap' in my specific scenario. Once this adjustment was made, the error disappeared.

After investigating the issue for a few minutes, I realized that simply running ng lint did not show any missing or failed imports. However, when I ran

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

, I was able to identify some other issues that led me to the error.

I had to manually go through each Page, Component, and Module to check for errors.

I toggled all the folders in VS Code and examined the "Problems" tab to correct the imports.

This problem arose when I duplicated a project and removed unnecessary references.

When Angular fails to provide a clear error description, turn to the TypeScript compiler for help. I found that this approach worked seamlessly for me, pinpointing the exact location and cause of the issue:

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

It's important to note that if you have multiple tsconfig files, make sure to use the one specifically designed for building your application. This could be tsconfig.app.json or another file indicated under the options.tsConfig section in angular.json.

Execute the build in development mode by running the command ng build, which will pinpoint the error location accurately.

Had a similar issue, but managed to resolve it by updating Angular to version 10.1.2 along with its dependencies.

Here's the snippet of my updated dependencies:

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"
  }

Each time I tried running ng build or ng serve after a major merge, this error kept popping up. The only solution that seemed to work for me was to use the 'divide and conquer' method. I created a new (test) branch and systematically isolated/deleted all new modules/components/files that were introduced during the merge. After each deletion, I would run ng build to check for errors. Once the error disappeared, I gradually reintroduced the previously deleted files in smaller chunks until pinpointing the source of the issue - turns out it was a simple incorrect import path.

Virendra Singh Rathore was spot on

The issue lies in incorrect imports. You may be attempting to import non-existent files or they might be located elsewhere :)

In my case, the error popped up after moving classes to a different file. VS code didn't pinpoint the error location. I had to manually search through all the files to find any faulty 'imports'.

Encountered a similar issue when transitioning from Angular 9 to 10.

Resolved the problem by updating development dependencies:

npm update --save-dev 

Here's a situation I encountered -->

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

I kept getting an error message saying "Cannot read property '0' of undefined". After some investigation, I realized it was due to incorrect paths. I fixed the issue by adjusting the paths as follows:

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

Encountering a similar problem, we exhausted all solutions listed before deciding to update our dependencies. This simple action led to a more detailed error message, pinpointing the root cause: an incorrectly set import path.

For me, it was a simple mistake. When I attempted to "repair" my "device", I initially imported it like this:

import DeviceRepairService from './device-repair.service';

Upon reviewing the code, I realized that adding "curly braces" resolved the issue.

import { DeviceRepairService } from './device-repair.service';