lapis-notes/plugin-registry
2
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

[docs/ui] Document plugin module loading and expose diagnostics #11

New issue
Open
opened 2026-06-02 08:21:15 +00:00 by steve · 0 comments
steve commented 2026-06-02 08:21:15 +00:00
Owner
Copy link

Source: Lapis plugin module loading plan, 2026-06-02.

Goal: make the migration understandable for plugin authors and visible to users/admins when a plugin loads or fails.

Scope:

  • Add developer docs for ESM plugins, CommonJS compatibility, shared host modules, and module loading architecture.
  • Document how to declare shared dependencies, what must be bundled, how ESM updates/reload work, and why sidecar has a smaller dependency surface.
  • Add Plugins UI badges for ESM, CommonJS compatibility, hybrid, sidecar, fallback used, missing dependency, deprecated host API, and reload required.
  • Add plugin detail diagnostics for selected host, format, entry, fallback, shared dependencies, missing/deprecated dependencies, asset URL mode, and version/hash URL.

Acceptance:

  • Plugin authors can build a valid ESM-first plugin from docs.
  • Users can see why a plugin loaded through fallback or failed dependency checks.
  • Deprecated/private host API usage is visible before it becomes a hard failure.
Source: Lapis plugin module loading plan, 2026-06-02. Goal: make the migration understandable for plugin authors and visible to users/admins when a plugin loads or fails. Scope: - Add developer docs for ESM plugins, CommonJS compatibility, shared host modules, and module loading architecture. - Document how to declare shared dependencies, what must be bundled, how ESM updates/reload work, and why sidecar has a smaller dependency surface. - Add Plugins UI badges for ESM, CommonJS compatibility, hybrid, sidecar, fallback used, missing dependency, deprecated host API, and reload required. - Add plugin detail diagnostics for selected host, format, entry, fallback, shared dependencies, missing/deprecated dependencies, asset URL mode, and version/hash URL. Acceptance: - Plugin authors can build a valid ESM-first plugin from docs. - Users can see why a plugin loaded through fallback or failed dependency checks. - Deprecated/private host API usage is visible before it becomes a hard failure.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lapis-notes/plugin-registry#11
No description provided.