TypeScript: Debug failure at walk

Bug Report

Running tsc causes an error message:

|| Error: Debug Failure.
||     at walk (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98559:38)
||     at Object.forEachChildRecursively (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:25491:27)
||     at /Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98475:20
||     at runWithCancellationToken (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98388:24)
||     at getJSSyntacticDiagnosticsForFile (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98472:20)
||     at getSyntacticDiagnosticsForFile (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98380:65)
||     at /Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98339:24
||     at Object.flatMap (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:428:25)
||     at getDiagnosticsHelper (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98335:56)
||     at Object.getSyntacticDiagnostics (/Users/derek/Workspace/***/node_modules/typescript/lib/tsc.js:98343:20)

🔎 Search Terms

Debug failure

🕗 Version & Regression Information

  • This is a crash
  • This changed between versions 4.3.5 and 4.8.2

💻 Code

tsconfig.js

{
  "extends": "expo/tsconfig.base",
  "compilerOptions": {
    "sourceMap": true,
    "strict": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["src/*"]
    }
  },
  "exclude": ["jest.config.js", "babel.config.js", "app.config.js"],
  "ts-node": {
    "require": ["tsconfig-paths/register"],
    "transpileOnly": true,
    "module": "commonjs",
    "target": "es2015",
    "esModuleInterop": true
  }
}

🙁 Actual behavior

Running tsc gives a Debug failure error.

🙂 Expected behavior

Running tsc should have worked without an error

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 18 (8 by maintainers)

Commits related to this issue

Most upvoted comments

For me the problem was coming from the js files in ./dist/bundles folder that was generated after running eas update, so I just excluded them "exclude": ["./dist"].

After a bit further digging, turning allowJs from true to false made the issue go away, but its not a fix though