The 'wwv create' command was fully interactive (prompts-only) and the
plugin-implementer agent's documented '--local' flag did not exist, so
agents fell back to slow manual scaffolding.
- Add a positional [pluginId] arg plus a flag for every prompt
(--display-name, --description, --category, --architecture,
--seeder-tier, --render-style) and a --yes guard that fails fast
instead of hanging when a required value is missing. Any omitted
flag still prompts, so interactive use is unchanged.
- Fix seeder output to the real community/private layout:
local-seeders/<tier>/packages/<name>/{package.json,tsup.config.ts,
src/index.ts}, exporting the canonical { name, cron, fn } shape with
name === plugin id (kebab-case) per ADR-0002. Previously it wrote a
bare seeder.mjs to the wrong path with an unusable context.emit stub.
- Update plugin-implementer.md: drop the bogus --local flag, document
the flag-based invocation and the correct seeder location, and note
the CLI build step for fresh worktrees.
- Bump CLI to 1.3.0 and fix the stale hardcoded --version string.
@worldwideview/wwv-cli
The official Command Line Interface for scaffolding and publishing WorldWideView plugins.
Usage
This CLI is designed to be run from within the worldwideview monorepo.
1. Scaffold a new plugin
node packages/wwv-cli/dist/index.js create
This command generates a new plugin directory with a boilerplate index.ts and package.json configured for the WorldWideView plugin architecture inside the local-plugins/ directory.
(Note: To create a built-in plugin inside packages/ instead, use the --core flag).
2. Publish a plugin
Once your plugin is ready for release, you can publish it to NPM. You can do this from within the plugin directory or directly from the project root.
From the plugin directory:
cd local-plugins/<plugin-name>
npm login
node ../../packages/wwv-cli/dist/index.js publish
From the project root: You can also run the CLI from the root by providing the plugin name:
node packages/wwv-cli/dist/index.js publish <plugin-name>
Custom NPM Organizations:
By default, plugins are scaffolded under the @worldwideview NPM scope. To publish to your own organization, use the --org flag:
node packages/wwv-cli/dist/index.js publish <plugin-name> --org my-username
This will permanently update your package.json to use @my-username and publish the package.
The publish command verifies that your package.json contains the required "worldwideview" manifest block and invokes npm publish --access public.
Development
To re-compile the CLI during development:
pnpm --filter @worldwideview/wwv-cli run build