omdsh-dev/web-components
web-components support
Lets a DSH Web profile mount plugin UI as native Custom Elements. The bundle adds the opt-in web-component row; when a profile enables it, the browser-side webComponent service mounts registered slot trees as Custom Elements while the adapter owns slot ownership, typed descriptors, property and event bindings, DOM outlets and incarnation lifetimes. The README documents the protocol reference and the invariant companion, and keeps the host/client artifact generation inside the package so a profile only consumes ready-made output.
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
README: the DSH Web Component adapter as an installable profile bundle. It exposes a browser-side webComponent service that mounts registered slot trees as native Custom Elements while keeping slot ownership, typed descriptors, property/event bindings, DOM outlets and incarnation lifetimes behind the adapter boundary. Slot host APIs, descriptor types, the browser runtime and the React renderer seam must come from the DSH build itself, and the README notes a legacy/ directory holding a source-compatible host integration patch for older DSH snapshots.
Details
- Repo: omdsh-dev/web-components
- Category: uncategorized
- Stars: 2
- Version: Bundle package @deepseek-ai/dsh-client-web-component (name did not resolve on the registry when checked 2026-09-17; repo 1★, last push 2026-08-09)
- Last push: 2026-08-09
- First seen: 2026-08-04
Recent updates
The README documents the repository shape, the bundle behavior and the limitations rather than a release-by-release table.
FAQ
- How is it installed?
- The README describes it as an installable profile bundle that adds a disabled web-component row, which a Web profile then enables with an explicit patch block; it does not print a dsh plugin add line and the package name returned 404 on 2026-09-17.
- What does the adapter provide?
- Per the README, a browser-side webComponent service that mounts registered slot trees as native Custom Elements while keeping slot ownership, typed descriptors, property/event bindings, DOM outlets and incarnation lifetimes behind the adapter boundary.
- Is it on for new profiles?
- No — the README says the row is added disabled and a Web profile enables it explicitly after the slot host and browser runtime are present.