wwv-lib-aviation and wwv-lib-incidents declared the SDK peer dep as "^1.4.10" (registry version), causing pnpm to install 1.5.0 nested inside each lib's node_modules. TypeScript resolved PluginContext from the nested 1.5.0 (which lacked getEngineUrl), not the workspace version, breaking CI type-checks for aviation and conflict-events plugins. Also includes docs: add property tag helper examples to local-plugins/README.md.
Local Plugins
This directory is a pnpm workspace for developing plugins locally without committing them to the main repository.
Quick Start
# Scaffold a new plugin
node packages/wwv-cli/dist/index.js create
# Start dev server (auto-discovers local plugins)
pnpm dev
How It Works
- Plugins here get full SDK type support via
workspace:*linking - The pre-dev script auto-builds each plugin with Vite
- Built bundles are copied to
public/plugins-local/ - The marketplace load API auto-discovers them in dev mode
- Everything in this directory is gitignored
Property Conventions
Use the SDK property tag helpers to give the Intel panel rich rendering for dates, URLs, images, and video. Without them, values display as plain text.
import { dtProp, urlProp, imageProp, videoProp } from "@worldwideview/wwv-plugin-sdk";
properties: {
// Dates — pass ISO 8601 strings
updated_at: dtProp(item.timestamp ?? null),
// External links
source_url: urlProp(item.url ?? null),
// Images
preview: imageProp(item.image_url ?? null),
// Video/streams
live_stream: videoProp(item.stream_url ?? null),
// Plain values — no helper needed
name: item.name,
count: item.count,
}
All helpers are null-safe — passing null or undefined returns null, which the panel skips.
See the SDK README for the full reference.
Publishing to NPM
When your plugin is ready to share, you can publish it directly to NPM from the root directory:
node packages/wwv-cli/dist/index.js publish <plugin-name> [--org <your-org>]