---
title: "DF8109: Renderer Module File Missing"
description: "The renderer module registered for dock type \"{type}\" does not exist at \"{file}\""
canonical_url: "https://devfra.me/errors/df8109"
---
# DF8109: Renderer Module File Missing

> The renderer module registered for dock type "\{type}" does not exist at "\{file}"

## Message

> The renderer module registered for dock type "`{type}`" does not exist at "`{file}`"

## Cause

An `initHub({ renderers })` registration points at a file that isn't on disk. Renderer modules are prebuilt, self-contained browser ES modules the hub serves verbatim at `<base>__renderers/<type>.mjs`; a missing bundle would make every client's lazy import 404 at mount time, so the hub fails fast at startup instead.

## Example

```ts
initHub({
  renderers: [
    { type: 'json-render', file: '/path/that/was/never/built.mjs' }, // ✗
  ],
})
```

## Fix

- Build the renderer package first; the bundle is a build artifact (e.g. `@devframes/json-render-ui`'s `dist/renderer/json-render.mjs`).
- Prefer the package's registration helper over a hand-written path; `jsonRenderUiRenderer()` from `@devframes/json-render-ui/hub` resolves the shipped bundle for you.

## Source

- [`packages/hub/src/node/initiate.ts`](https://github.com/devframes/devframe/blob/main/packages/hub/src/node/initiate.ts): `resolveRendererRegistrations()` throws when the resolved `file` fails the existence probe.


## Sitemap

See the full [sitemap](https://devfra.me/sitemap.md) for all pages.