The browse and native backends were dual-face packages: a Node backend plus a browser surface under one tsconfig that referenced Client packages. That put Client projects — and through them the Client runtime — inside the Host compiler aggregate, which builds before the generated Remote contributions exist. Each browser half moves to its own Client package, and both backends become Node-only. The interaction is still one choice: the adaptive chooser mounts the backend and its surface as a pair of Loader entries and tears both down in reverse, so a resolved kind still swaps both faces. Compositions that pin an interaction directly now pin the pair, and the chooser's runtime-string package list keeps naming everything a composing app must resolve.
14 lines
633 B
YAML
14 lines
633 B
YAML
# Loader overlay for the real-host smoke (`dsh web --patch`): pin the
|
|
# in-browser directory picker. The shipped row is `-auto`, which resolves to
|
|
# the native OS chooser on a loopback bind with a local display — an
|
|
# interaction a Playwright page cannot drive, so the resolved backend would
|
|
# otherwise decide whether the smoke passes. The disable+insert pair mirrors
|
|
# apps/web/tests/scaffold.ts.
|
|
- id: directory-picker
|
|
disabled: true
|
|
- insert:
|
|
- id: directory-picker-browse
|
|
name: '@deepseek-ai/dsh-host-directory-picker-browse'
|
|
- id: ui-directory-picker
|
|
name: '@deepseek-ai/dsh-client-ui-directory-picker'
|