DF8200: Terminal Session Already Registered
Terminal session with id "{id}" already registered
Message
Terminal session with id "{id}" already registeredCause
ctx.terminals.register(session) or ctx.terminals.startChildProcess(opts, terminal) was called with an id that another session already owns. Terminal ids are unique per hub context.
Fix
- Pick a different session id (namespace under your tool:
my-tool:build-server,my-tool:tests, …). - If you want to reuse an existing session's slot,
ctx.terminals.remove(session)first.
Source
packages/hub/src/node/host-terminals.ts—DevframeTerminalsHost.register()andstartChildProcess()throw when the id is already taken.
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.
DF8201: Terminal Session Not Registered
Terminal session with id "{id}" not registered