Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

ng build fails with TS1005 inside @types/babel__traverse

ErrorERROR in node_modules/@types/babel__traverse/index.d.ts

Short answer

The compiler could not parse a declaration file in node_modules, which almost always means the @types package was written for a newer TypeScript than yours. Upgrade TypeScript to the range your Angular version supports, or pin the @types package to an older release.

  • Applies to Angular 20, TypeScript 5.8, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Compare the TypeScript version you run with the version of the failing @types package.

    npx tsc -v
    npm ls typescript @types/babel__traverse
  2. 2Match what you see, then jump to its fix

    1. 1tsc -v prints a version below the range your Angular release supportsTypeScript is older than the declarations needFix
    2. 2The project is locked to an older Angular and TypeScriptYou cannot upgrade TypeScript right nowFix

What does the error look like?

  • ERROR in node_modules/@types/babel__traverse/index.d.ts
  • error TS1005: ']' expected.

Cause 1 of 2

TypeScript is older than the declarations need

1Check

DefinitelyTyped tests packages only on TypeScript versions less than 2 years old, so a package can use syntax an old compiler cannot parse. Compare tsc -v with the Angular version table.

npx ng version

2Fix

Move TypeScript to the range Angular lists for your version. Angular 20.2 and 20.3 list >=5.8.0 <6.0.0.

npm install --save-dev typescript@">=5.8.0 <6.0.0"

3Verify

Rebuild.

npx ng build

Confirmed by angular.dev

Did this fix it?

Cause 2 of 2

You cannot upgrade TypeScript right now

1Check

Older releases of an @types package stay available, so you can install one from the time your TypeScript was current.

npm view @types/babel__traverse versions --json

2Fix

Install an older release of the @types package, and pin it exactly so npm does not float it forward.

npm install --save-dev --save-exact @types/babel__traverse@<older-version>

3Verify

Rebuild after the install.

npx ng build

Confirmed by github.com

Did this fix it?

How do I stop it coming back?

  • Upgrade Angular and TypeScript together and keep them inside the documented range.
  • Commit the lockfile so a fresh install does not pull a newer @types package.
  • Read the Angular version table before you update TypeScript on its own.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

cdk synth says --app is required

--app is required either in command-line, in cdk.json or in ~/.cdk.json

The CDK CLI needs a command that runs your app and finds it in three places: the --app option, cdk.json in the project folder, or cdk.json in your home folder.

3 causes, each with a fix

Back end

Mocha or Node cannot find ts-node/register

Error: Cannot find module 'ts-node/register'

Node resolves ts-node/register from your project's node_modules, so the package must be installed there, next to typescript.

2 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.