# Enable Debugging In VS Code

## Introduction

#### An integrated development environment for WASM.

## How to debug this extension

> Note that when you download and decompress to get .vsix file from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases). It's by default that the `source debugging` feature is not enabled. If you want to enable the `source debugging` feature of this extension, you could download `lldb` from [our release](https://github.com/bytecodealliance/wasm-micro-runtime/releases) (This is the recommended way, and you could do it with a single click in VS Code). Then if you want to use your customized lldb patch, you could build your own version of `lldb` and then follow this [instruction](/document/wamr-in-practice/tutorial/debugging-and-ide-support/wamr-ide/debug.md) to put them in the correct path

#### 1. open `VSCode_Extension` directory with the `vscode`

```xml
File -> Open Folder -> select `VSCode_Extension`
```

#### 2. run `npm install` in `terminal` to install necessary dependencies.

#### 3. click `F5` or `ctrl+shift+D` switch to `Run and Debug` panel and click `Run Extension` to boot.

## Code Format

`prettier` is recommended and `.prettierrc.json` has been provided in workspace. More details and usage guidance please refer [prettier](https://prettier.io/docs/en/install.html)

You can run following commands in current extension directory to check and apply

```shell
# install prettier firstly
npm install --save-dev prettier
# check format
npm run prettier-format-check
# apply
npm run prettier-format-apply
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wamr.gitbook.io/document/wamr-in-practice/tutorial/debugging-and-ide-support/wamr-ide/vscode-extension.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.