Repository navigation
Debugging
Jens Fischer edited this page May 17, 2019
·
3 revisions
A wide variety of Haxe targets can be debugged with Haxe sources in VSCode:
- HashLink, using the HashLink Debugger extension
- HXCPP, using the HXCPP Debugger extension
- Flash, using the Flash Debugger extension
- JavaScript, using the sourcemaps generated by Haxe and the built-in Node debugger or one of the extensions for remote browser debugging (Chrome, Firefox, ...)
There's also a debugger for Haxe 4's new macro interpreter called "Eval" built directly into vshaxe. This can be used for:
- debugging all the different kinds of macros (build, expression, init)
- debugging programs executed in the interpreter using
--interpor--run

With a minimal launch.json, the debugger is started using the haxe specified by the "haxe.executable" setting and with the arguments from the currently selected Haxe Configuration:
{
"version": "0.2.0",
"configurations": [
{
"name": "Haxe Interpreter",
"type": "haxe-eval",
"request": "launch"
}
]
}To override the arguments that are used, you can set "args", for instance "args": ["build.hxml", "--interp"].
Setup
Features
- Tasks
- Debugging
- Commands
- Dependency Explorer
- Auto Indentation
- Completion
- Postfix Completion
- Snippets
- Code Generation
- Signature Help
- Hover Hints
- Go to Definition
- Go to Type Definition
- Go to Implementations
- Peek Definition
- Find All References
- Rename Symbol
- Document Symbols
- Workspace Symbols
- Outline
- Folding
- Diagnostics
- Code Actions
- Code Lens
- Formatting
- Extension API
- Inlay Hints
- Refactoring
- Inline Values
Noteworthy Releases