Debug failure at walk
See original GitHub issueBug 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
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:18 (8 by maintainers)
Top Results From Across the Web
TypeScript Compiler fails with "Debug Failure. False ...
Open test.ts from the attached project. TypeScript Service and Compiler should be enabled. No errors are highlighted, Console contains the next error:
Read more >94618 – [8/9 Regression] '-fcompare-debug' failure (length) with
Though, a slight advantage of the patch as is is that it will do any insn walk only if two conditions are met,...
Read more >Debugging Failing Tests and Test Pipelines - GitLab
Guidelines for investigating end-to-end test pipeline failures. ... Pipeline triage DRI is responsible for analyzing and debugging test pipeline failures.
Read more >How to debug for absolute beginners - Visual Studio
An exception is an unexpected event encountered when running code, typically an error of some kind. A debugging tool can take you to...
Read more >Debugging - Cypress Documentation
You can see a walk-through of debugging some application code from Cypress in ... Cypress prints several pieces of information when an error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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"]
..js
files that don’t contain JS? That seems like a bad idea, but I don’t think we should crash with them in any case.