DF8110: Renderer Type Is Not URL-Safe
Message
Dock type "{type}" is not a servable renderer-module name; the hub serves each module at<base>__renderers/<type>.mjs
Cause
An initHub({ renderers }) registration carries a type that can't become a URL segment. The hub derives each module's serving path (and the manifest's importFrom) from the type, so : and * (route-pattern markers to the underlying router) or separators like / would break the route.
Example
initHub({
renderers: [
{ type: 'my:renderer', file: bundle }, // ✗ `:` is a route-param marker
],
})Fix
Use a route-safe dock type: letters, digits, _, -, and . only (e.g. json-render, my-renderer). The dock entries' type discriminator must match, so pick the safe name once, in the package that declares the type.
Source
packages/hub/src/node/initiate.ts:resolveRendererRegistrations()rejects atypefailing the[\w.-]+segment check.
DF8109: Renderer Module File Missing
The renderer module registered for dock type "{type}" does not exist at "{file}"
DF8111: Bare-Specifier Client Script Without Host Resolution
Dock "{id}" declares the bare-specifier client script "{specifier}", but this host advertises no client-module resolution; the browser cannot resolve a bare npm specifier natively, so the script will fail to load.