新机器ng build报错：cannot read property 'kind' of undefined 求助

Hey there, let's dig into this issue you're facing. That error message is a classic sign that the TypeScript compiler (or Angular's build tooling that relies on it) is hitting a snag while parsing your code's abstract syntax tree (AST). The kind property is part of TS AST nodes, so when it throws "cannot read property 'kind' of undefined", it means the compiler expected a valid AST node but got undefined instead—usually due to version mismatches, corrupted cache, or subtle syntax/compatibility issues.

Here are actionable troubleshooting steps to narrow this down:

• Exact dependency version matching
  First, cross-check the exact versions of Node.js, npm, Angular CLI, and TypeScript between your working machine and the new one. Even minor version differences can break compatibility. Run these commands on both machines to compare:

  node -v
  npm -v
  ng version
  tsc -v
  

  Use a version manager like nvm (for Node) to lock into the exact versions from your working environment, then reinstall dependencies.

• Wipe caches and rebuild dependencies
  Corrupted npm or Angular cache is a common culprit. Run these commands in your project root:

  # Clear npm cache
  npm cache clean --force
  # Clear Angular CLI cache
  ng cache clean
  # Delete existing dependencies and lock file
  rm -rf node_modules package-lock.json
  # Reinstall fresh
  npm install
  

• Check for global vs local dependency conflicts
  Sometimes a globally installed Angular CLI version clashes with your project's local version. Run ng version—look for "Global Angular CLI" vs "Local Angular CLI" entries. If they don't match, use npx ng build to force using your project's local CLI version instead of the global one.

• Validate TypeScript configuration
  Double-check your tsconfig.json (and tsconfig.app.json if using Angular) for any settings that might be incompatible with your new environment. Pay attention to target, lib, strict mode flags, and any experimental features—these can trigger AST parsing errors if they don't align with your TypeScript version.

• Isolate the problematic code/module
  Even if you don't see obvious issues in your code, a third-party dependency or a subtle syntax quirk (like a deprecated TS feature that's now broken in a newer version) could be the cause. Try commenting out sections of your app or disabling lazy-loaded modules one by one, running ng build after each change to pinpoint which part triggers the error.

• Check OS-specific quirks
  If your working machine and new machine run different OSes (e.g., Windows vs Linux/macOS), watch out for:

  • Case-sensitive file paths: Linux/macOS care about uppercase/lowercase in imports, while Windows doesn't. A mismatched import like import { Foo } from './foo' vs ./Foo could break parsing.
  • Line ending differences: While rare, inconsistent line endings can sometimes throw off the compiler. Ensure your project uses consistent line endings (LF or CRLF) across both machines.

• Try minor version adjustments
  If matching exact versions still fails, try a small upgrade or downgrade of Angular CLI or TypeScript. For example, if you're on TypeScript 4.8.4, try 4.8.3 or 4.9.0—sometimes a patch version fixes edge-case parsing bugs.

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