You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.8 KiB
1.8 KiB
| title | layout | nav_exclude |
|---|---|---|
| Development Notes | default | true |
Development Notes
Releasing New Versions
To release a new version:
- Update
versioninpackage.json. - Run
npm run versionto updatemanifest.json&versions.json.manifest.json: holds the new version number and the minimum Obsidian version required for your latest release.versions.json: holds the history of version numbers and their minimum Obsidian version, so older versions of Obsidian can download an older version of your plugin that's compatible.
- Create new GitHub release using your new version number as the Tag version. Use the exact version number, and don't include a prefix
v. See the following example: obsidian-sample-plugin. - Upload the files
meld-encrypt-<ver>.zip,manifest.json,main.js, andstyles.cssas binary attachments. - Publish the release.
Adding Your Plugin to the Community Plugin List
To add your plugin to the community plugib list:
- Publish an initial version.
- Make sure you have a
README.mdfile in the root of your repository. - Make a pull request at obsidian-releases to add your plugin.
How to Use
- Clone this repository.
- Run
npm ioryarnto install dependencies. - Run
npm run devto start the compiler in watch mode.
Manually Installing the Plugin
Copy the files main.js, styles.css, and manifest.json to your vault at VaultFolder/.obsidian/plugins/your-plugin-id/, replacing your-plugin-id with the actual ID of your plugin.
If the your-plugin-id folder does not exist, create it before copying the files.
API Documentation
For detailed API Documentation, see the Obsidian API repository.