Manifest

Each community plugin lives in its own folder and declares metadata in manifest.json.

{
  "id": "example-plugin",
  "name": "Example Plugin",
  "version": "0.1.0",
  "minAppVersion": "1.7.7",
  "main": "main.js"
}

Recommended fields

• id: stable lowercase plugin id.
• name: user-facing name.
• version: plugin version.
• minAppVersion: lowest Lapis version the plugin supports.
• main: JavaScript entrypoint.
• supportedRuntimes: optional runtime declaration.
• requiredCapabilities: optional brokered capabilities such as vault I/O or settings.

Keep ids stable. Changing a plugin id creates a different plugin from the user’s point of view.

Lapis namespace

Lapis-native extensions can add an optional lapis object for VS Code-style contribution indexing, lazy activation, declarative settings, and language-service declarations. See Lapis manifest contributions for the full reference.