Debugging a Flex Plugin with VS Code

This is a guide on how to set up VS Code to easily debug your Flex Plugin locally. This tutorial builds off of the Plugin from the Plugin Development Quickstart.

When debugging your Plugin, it is useful to set breakpoints in your application and to walk through it step-by-step. Luckily, VS Code already comes with a built-in debugger.

This tutorial requires that you have an existing Flex Plugin. It also requires that you already have VS Code installed on your operating system.

Create launch.json

Open your Plugin folder in VS Code, then switch to the Debugger panel. There are currently no launch.json files. Click on the Run and Debug button and select Web App (Chrome). This will automatically create a launch.json inside .vscode folder and open the file for you.


Then, replace the value of URL in launch.json with http://localhost:3000 and save the file.

Start Debugging

Now that we have the Debugger set up, it's time to run our dev-server and launch the debugger.

First, start your Flex plugin using twilio flex:plugins:start. You may close the browser that this script starts as we'll launch another one shortly.

Next, go to the Debugger panel of your VS Code again. This time, in the dropdown menu, you should see a Chrome or Launch Chrome option. Make sure it is selected, and press the green play button.


This will launch a new Chrome page and start your application. You can now log into your Flex instance.

Set Breakpoints

While running in debug mode, you will see a debugger toolbox in the top center of the VS Code editor.


Open the file where you'd like to set a breakpoint. Hover your cursor to the left of the line number. A little red dot should appear. Click to place the breakpoint. Now, click the green "refresh" button on the toolbox to restart the app.


That's it! You now have a breakpoint at this step of your application. You should be able to see the variables and the call stack, as well as step into the methods.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Thank you for your feedback!

Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

Sending your feedback...
🎉 Thank you for your feedback!
Something went wrong. Please try again.

Thanks for your feedback!