New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

obsidian-undocumented

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

obsidian-undocumented

Undocumented/private API definitions for Obsidian.md

latest
obsidian-1.1.9
Source
npmnpm
Version
0.1.3
Version published
Maintainers
1
Created
Source

obsidian-undocumented

latest supported version total downloads

An extension to the official obsidian type definitions that provides access to undocumented and internal Obsidian APIs.

This project aims to provide quality typings that are relevant across a range of public Obsidian versions.

Installation

Use npm or yarn to install type definitions for undocumented Obsidian APIs:

npm install obsidian-undocumented

Usage

Import the type definitions and use the as keyword to cast the official, documented API type into the unofficial one.

import {Plugin} from "obsidian";
import {App} from "obsidian-undocumented";

export default MyPlugin extends Plugin {
	async onload() {
		// Get the enabled instance of the "other-plugin" plugin.
		const otherPlugin = (this.app as App).plugins.getPlugin("other-plugin");
		otherPlugin.doSomething();
	}
}

Unsafe API

There are two flavors of type definitions available: the default (safe) definitions, and the unsafe definitions. The safe definitions provide typings for harmless functions and fields, and the unsafe definitions provide typings that can accidentally break Obsidian or be abused to manipulate other plugins.

The definition flavors can be picked by either importing obsidian-undocumented for the safe definitions or obsidian-undocumented/unsafe for the unsafe ones.

Example:

import {Plugin} from "obsidian";
import {App} from "obsidian-undocumented/unsafe";

export default MyPlugin extends Plugin {
	async onload() {
		(this.app as App).plugins.disablePlugin(this.manifest.id);
	}
}

Targeting Specific Obsidian Versions

If your plugin has different logic for different Obsidian versions, it is possible to select type definitions matching the specific version. All of the definitions exported by obsidian-undocumented contain a generic parameter V, which should be a string for one of the supported versions.

If the parameter is omitted, type definitions will be selected for the latest Obsidian version that is supported by this package.

Example:

import { Plugin, apiVersion } from "obsidian";
import { App, v1_0_0 } from "obsidian-undocumented";

export default class ExamplePlugin extends Plugin {
	async onload() {
		if (apiVersion === '1.0.0') {
			const app = this.app as App<v1_0_0>;
			// Do something specific to API version 1.0.0
		}
	}
}

Supported Versions

Undocumented API type definitions are available for the following Obsidian versions:

  • 1.1.9 (default)
  • 1.1.8
  • 1.0.3
  • 1.0.0

There are currently no plans to support pre-release or beta versions of Obsidian.

Keywords

obsidian

FAQs

Package last updated on 21 Feb 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts