INCISOR® FAQs & Tutorials →
FAQs & Tutorials / FAQ
FAQ · Debugging

Can I debug my project from my code editor?

Set a breakpoint in your own TypeScript or JavaScript, press a key in your game, and land right on that line with your variables and call stack in front of you, all without leaving your editor.

FAQDebuggingVS CodeWebStormTypeScriptSettings
Short answer

Yes. Incisor can open a debugging port on your computer. Turn on allowEditorDebugging in Application Settings, restart Incisor, and attach your editor to that port. For VS Code, Incisor even writes the attach configuration for you.

Before you start

Incisor 2026.10.26.15.33.40 or later

Editor debugging isn't available in earlier versions. Use Incisor menu → Check for Updates to update.

Source maps on

Your breakpoints map to your own files through source maps. In Project Settings, keep generateSourceMaps on, and turn removeComments and removeWhiteSpace off for the configuration you're running.

Whitespace removal must be off for now. Soon, whitespace removal will only happen when you publish, and this requirement will go away.

Know the risk. The debugging port is only open to your own computer, but any program on that computer, including programs run by other user accounts, can connect to it and run code inside your projects. Turn it on only on a machine you trust, and turn it off when you're done debugging.

1Turn on editor debugging

This step is the same whichever editor you use.

The Incisor menu open, with Application Settings highlighted
Incisor menu → Application Settings...
Application Settings with allowEditorDebugging checked and editorDebuggingPort set to 9222 in the security group
The security group holds both debugging settings.
  1. Open Application Settings from the Incisor menu (the logo at the far left of the menu bar).
  2. Under security, tick allowEditorDebugging. Incisor asks you to confirm that you accept the risks. Choose Yes.
    Verification prompt: By enabling this feature, you agree to assume responsibility for all of the associated risks. Do you wish to continue?
  3. Leave editorDebuggingPort at 9222 unless another program on your computer already uses that port. Any whole number from 1024 to 65535 works.
  4. Press Save and Restart. Both settings take effect only when Incisor starts. Save and Refresh keeps Incisor running and applies them the next time it starts.
    Restart Incisor prompt with Cancel, Save and Refresh, and Save and Restart buttons

2Connect your editor

Every editor connects to the same port. Only the setup is different.

VS Code

When you open a project with editor debugging on, Incisor adds an Attach to Incisor configuration to the project's .vscode/launch.json. All you have to do is start it.

  1. Open the project folder in VS Code (the folder itself, not a parent folder), so VS Code finds the project's .vscode folder.
  2. Go to Run and Debug, choose Attach to Incisor from the dropdown, and press the green play button (or F5).
    VS Code Run and Debug dropdown with Attach to Incisor selected
  3. VS Code lists the open Incisor tabs. Pick your project, not the Control Center.
    VS Code tab picker listing INCISOR Control Center and INCISOR Incisor Slot Template TS, with the project selected
  4. Click in the gutter to set a breakpoint in one of your files, then run the code that reaches it.
VS Code paused on a breakpoint in ProjectMain.ts, showing local variables and the call stack
Paused on a breakpoint in ProjectMain.ts. The Variables and Call Stack panels show your own TypeScript, not compiled output.

What Incisor writes for you

The generated launch.json open in VS Code, containing the Attach to Incisor configuration
  • launch.json: the Attach to Incisor entry is kept current by Incisor, including your port and the source-map paths for your files. Any other configurations you add are left alone.
  • tasks.json (TypeScript projects): an Incisor TypeScript Check task runs when you open the folder and keeps watching your files. Type errors appear in the Problems panel as you work. Your own tasks are left alone too.
A TypeScript error underlined in ProjectMain.ts and listed in the Problems panel
The TypeScript Check task catches a typo before you even run the project.

WebStorm

WebStorm attaches with its built-in Attach to Node.js/Chrome configuration. You set it up once per project.

  1. Open the project folder in WebStorm.
  2. Choose Run → Edit Configurations...
    WebStorm Run menu with Edit Configurations highlighted
  3. Press + and choose Attach to Node.js/Chrome. Give it a name such as Incisor, leave Host as localhost, and set Port to your editorDebuggingPort (9222 by default). Leave everything else as it is and press OK.
    Run/Debug Configurations with the Add New Configuration list open and Attach to Node.js/Chrome highlighted
    An Attach to Node.js/Chrome configuration named Incisor, with host localhost and port 9222
  4. Select Incisor in the run configuration dropdown and press the Debug button (the bug), or choose Run → Debug 'Incisor'. WebStorm lists the Incisor pages. Pick your project, not the Control Center or the tab bar.
    WebStorm Choose Page to Debug list with the Incisor Slot Template TS project selected
  5. Click in the gutter to set a breakpoint in one of your files, then run the code that reaches it.
WebStorm paused on a breakpoint in ProjectMain.ts, with the call stack and local variables in Threads & Variables
Paused on a breakpoint in ProjectMain.ts, with the call stack and variables in Threads & Variables.

Incisor doesn't write this configuration for you, as it does for VS Code. If you change editorDebuggingPort, update the port here too.

Incisor's console, in WebStorm

While attached, the Console tab of the Debug window shows your project's console output, including the TypeScript errors Incisor reports.

A TypeScript error from Incisor shown in WebStorm's Debug Console

Good to know

Projects open stopped (by default), so press Run

Live View showing a play button and the words press to run

Nothing runs until you press Run in Live View, which gives you time to attach and set breakpoints before your startup code runs. To have projects start running as soon as they open, turn on runProjectOnOpen in Application Settings.

Choosing stopProjectOnException

This Application Setting decides what happens when your code throws an error:

On

Incisor stops the project at the error. This keeps the Incisor inspector running smoothly, so it's a good everyday setting.

Off

The project keeps running past the error, so you can watch what happens next in your debugger. Use this to track down the trickier bugs.

Troubleshooting

“Editor debugging port in use”

Incisor shows this when another program already holds the port. Your editor can't attach until Incisor opens its own port. Pick a different editorDebuggingPort in Application Settings and restart Incisor. In VS Code, the Attach to Incisor configuration picks up the new port automatically.

No “Attach to Incisor” in VS Code

  • You're on Incisor 2026.10.26.15.33.40 or later.
  • allowEditorDebugging is on and Incisor has been restarted since you turned it on.
  • Source maps are on: generateSourceMaps on, removeComments and removeWhiteSpace off.
  • You've opened the project in Incisor since then (that's when the configuration is written), and VS Code has the project folder itself open.

Breakpoints don't get hit

  • You picked your project's tab, not the Control Center.
  • The project is running (press Run in Live View).
  • Source maps are on, as above.

My port setting was ignored

The port must be a whole number from 1024 to 65535. Anything else falls back to 9222.