@appthen/vibe-workspace
v0.1.16
Published
A configurable IDE-style workbench component library
Readme
@appthen/vibe-workspace
AppThen Workbench runtime and offline extension development toolkit.
For Extension Developers
The recommended starting point is the generated offline workspace:
pnpm dlx @appthen/vibe-workspace init extension-workspace --template full
cd extension-workspace
pnpm install
pnpm doctor
pnpm devThe workspace supports multiple local extensions and does not require marketplace access during development. Read the generated AGENTS.md before making changes.
Extension Commands
appthen-extension init [dir] [--id app.id] [--template basic|full]
appthen-extension dev [--port 5177]
appthen-extension doctor [--json]
appthen-extension validate
appthen-extension test [extensionId]
appthen-extension build [extensionId]
appthen-extension pack [extensionId]
appthen-extension publish [extensionId ...] --server <url> --tenant <tenantId> [--bump [patch|minor|major]]
appthen-extension install <package-file> --server <url> --tenant <tenantId>publish accepts one or more extension ids (or --all) for a non-interactive run. In a terminal, running it without ids opens an interactive picker: choose one or several extensions (or all), then choose the version strategy.
On the dev channel you normally do not need --bump: the server adds a content fingerprint to the CDN path (…/dev/<version>-<hash>/), so changed bytes get a new URL (no stale cache) while identical bytes map to the same path (idempotent re-publish). Older dev build directories are pruned automatically — only the current and previous build are kept. --bump [patch|minor|major] still works when you want an explicit, stable version (it rewrites the source manifest.json and the built manifest). Non-TTY runs (CI, pipes, --json) skip the picker and keep the old default (all extensions, no bump).
开发 Workbench SDK 本身时,不需要发布 npm。先在 SDK 仓库执行 pnpm run build:lib -- --watch,再从扩展工作区指向本地 SDK:
pnpm dev -- --package-root /path/to/vibe-workspacepublish uploads and updates the tenant extension record. It does not mount the extension into a Workbench unless --install-tenant is provided. Workbench mounting and permissions are configured separately.
Stable Extension API
External extensions should use:
ctx.capabilities.registerSidebarViewctx.capabilities.registerEditorViewctx.capabilities.registerContributionctx.capabilities.registerFrontendToolHandlerctx.views.openEditorctx.linksctx.runtimeandctx.auth
External extensions should not depend on extensionRegistry, eventBus, workspaceEditorService, or registerMainView.
Documentation
- Extension development specification
AGENTS.mdis generated in every workspace byappthen-extension init.- Multi-column workspace rules
Local Development Of This Repository
pnpm install
pnpm typecheck
pnpm run build:lib