Skip to content

About

First-party plugins for applications built on the Lapis framework

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

551 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Lapis Plugins

This monorepo contains the independently versioned first-party plugins for the Lapis application framework. Applications compose the plugins they need by installing their npm packages and registering an app-owned static plugin profile. The same package version can also be installed at runtime from its signed .lapis-plugin release asset.

Packages

Package Runtime plugin ID
@lapis-notes/bases bases
@lapis-notes/bookmarks bookmarks
@lapis-notes/graph lapis-graph
@lapis-notes/history history
@lapis-notes/markdown markdown
@lapis-notes/markdown-lint lapis-markdown-lint
@lapis-notes/search search
@lapis-notes/source-editor lapis-source-editor
@lapis-notes/spellcheck spellcheck
@lapis-notes/transcripts lapis-transcripts
@lapis-notes/wordcount wordcount

The package name and runtime ID intentionally remain separate compatibility contracts. Runtime IDs are not changed during extraction.

The former shared AI package is retired; current AI belongs to Tauri and App Profile native chat in their owning hosts. Its publication tombstone remains in release tooling. See the retirement contract and Notes' progress record for pending consumer removal and release gates.

Development

The repository has one Storybook. Stories remain grouped by owning package under stories/plugins. Package manifests use registry semver ranges even during local development; prerelease validation supplies framework tarballs in an isolated temporary consumer without changing publishable manifests.

pnpm audit
pnpm packages:check
pnpm spec:check
pnpm check
pnpm test
pnpm build
pnpm build-storybook

pnpm ci:packages runs the package build, check, and test graph through one bounded Turbo invocation. pnpm ci:release adds policy, specification, release-tool, npm-pack, signed archive, verification, and static Storybook gates. Turbo defaults to half the available processors, capped at four; set TURBO_CONCURRENCY to a positive number or percentage to override it.

For Linux parity, pnpm ci:container uses the digest-pinned public CI image and lockfile-keyed local volumes. Copy .env.example to the ignored .env and add the two secret values to opt into the shared remote cache. Without a complete set of TURBO_API, TURBO_TEAM, TURBO_TOKEN, and TURBO_REMOTE_CACHE_SIGNATURE_KEY, the runner performs normal local execution without remote-cache access. Do not commit .env.

See RELEASING.md for the manual publication gate and release asset contract.

Local checks

Portable checks, builds and tests default to Docker. See validation for image preparation, remote execution, explicit native runs and story composition checks.

Agent skills

Bases, Canvas and Markdown contribute Lapis-specific skills in their npm and signed plugin packages. Use Install plugin skills in the application command palette to install enabled plugins' workflows under the vault's .agents/skills. Use Update plugin skills after upgrading plugins. Updates preserve complete skill directories with local edits, added/deleted files or missing installation receipts, and report the skipped names. They never upgrade plugins themselves.

The authenticated lapis skills list, lapis skills install and lapis skills update commands provide the same native service for a selected --vault; --skill selects one workflow. The host owns the CLI skill.

About

First-party plugins for applications built on the Lapis framework

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages