obsidian-plugin-dev

To set up an Obsidian plugin with TypeScript and esbuild, configure the esbuild bundler and tsconfig to compile your src/main.ts entry point into a manifest-compatible bundle. This ensures your plugin loads correctly within the Obsidian vault environment.

Registering commands and settings tabs in an Obsidian plugin involves using the Plugin class setup and register* helpers. This pattern ensures everything cleans up on unload, maintaining a stable lifecycle for commands, views, modals, and settings configurations.

The requestUrl function works for making HTTP requests in Obsidian plugin development by providing a platform-safe API for desktop and mobile. It replaces standard fetch calls, ensuring safe network behavior across different Obsidian runtime environments.

Yes, you can use the Vault API to read and write files in your Obsidian plugin. The API provides adapter usage and event listeners for Vault and Workspace interactions, allowing safe file modifications while respecting the plugin lifecycle hooks.

Obsidian plugins leave dangling event listeners after uninstall when register* cleanup conventions are not followed. Using the register* helpers during Plugin class setup ensures all commands, views, and Vault events are properly disposed of on unload.

The best way to handle Platform detection for mobile-safe Obsidian plugins is using the Platform API alongside requestUrl requirements. This approach distinguishes between desktop and mobile environments, ensuring safe HTTP and crypto behavior across devices.