obsidian-plugin/mnaoumov_obsidian-advanced-debug-mode
1
0
Fork 0
mirror of https://github.com/mnaoumov/obsidian-advanced-debug-mode.git synced 2026-07-22 05:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
mnaoumov_obsidian-advanced-.../demo-vault/05 More debug tools.md
Michael Naumov 715fe7ed5b feat: add demo vault 
Add a developer-focused demo vault that shows how Advanced Debug Mode enriches
the DevTools console. Notes are numbered basic to advanced and cover debug mode,
long stack traces (with a Run button that throws through async boundaries), async
long stack traces, long-running-task timeouts, mobile DevTools, debug namespaces,
and every setting. A no-app integration suite keeps the notes in sync with the
PluginSettings surface. The root README documents the three ways to open it.
2026-07-20 09:19:21 -06:00

1.5 KiB
Raw Blame History

Docs

More debug tools

Two smaller features round out the plugin. Neither has its own setting - they are surfaced through a command and the settings tab.

DevTools on mobile

Obsidian's desktop app has DevTools built in; the mobile app does not, which makes debugging a plugin on a phone or tablet painful. Advanced Debug Mode adds a floating DevTools button to the mobile app so you can inspect the console and elements without tethering the device to a desktop.

  • Run Advanced Debug Mode: Toggle DevTools button from the command palette to show or hide the button.
  • On desktop this is unnecessary (Ctrl + Shift + I already opens DevTools), so the button is aimed at mobile.

Debug namespaces

Many plugins - and obsidian-dev-utils itself - use the debug library to emit console.debug messages that are hidden unless their namespace is enabled. Advanced Debug Mode adds a UI for managing those namespaces so you can switch specific channels of debug output on and off without editing localStorage by hand.

  • Open Settings -> Community plugins -> Advanced Debug Mode and find the debug-namespaces section.
  • Enable a namespace, reproduce the behavior, and watch the matching console.debug output appear in DevTools.

For the full explanation of debug namespaces, see the obsidian-dev-utils debugging guide.

Head to 06 Settings for the settings-backed features.