mirror of
https://github.com/mnaoumov/obsidian-advanced-debug-mode.git
synced 2026-07-22 05:44:00 +00:00
715fe7ed5b
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.
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
[Docs](https://github.com/mnaoumov/obsidian-advanced-debug-mode/)
|
|
|
|
# Debug mode
|
|
|
|
Obsidian has a built-in **debug mode**. When it is off (the default), Obsidian strips the inline source maps from the plugins it loads, so any error you see in DevTools points at minified, bundled code that is almost impossible to read. Turning debug mode on keeps those source maps, so stack traces point back at the plugin's real source files.
|
|
|
|
Advanced Debug Mode gives you a one-click switch for it.
|
|
|
|
## How to turn it on
|
|
|
|
1. Open the command palette (`Ctrl`/`Cmd` + `P`).
|
|
2. Run **Advanced Debug Mode: Open plugin settings** (or open **Settings -> Community plugins -> Advanced Debug Mode**).
|
|
3. Toggle **Debug mode** on.
|
|
|
|
Obsidian reloads the plugins so the source maps take effect.
|
|
|
|
## How to see the difference
|
|
|
|
1. Open DevTools (`Ctrl`/`Cmd` + `Shift` + `I`).
|
|
2. With debug mode **off**, trigger an error from any plugin (the **Run** button in [[02 Long stack traces]] is a good one) and note that the stack frames point at bundled `main.js` lines.
|
|
3. Turn debug mode **on**, trigger the same error, and note that the frames now point at the original `.ts` source files.
|
|
|
|
Once debug mode is on, move on to [[02 Long stack traces]] to see the plugin's headline feature.
|