stefanohe/deepseek-harness-datasecure--packages-boot-hmr ↗★ 1
@deepseek-ai/dsh-hmr
Coordinated module and profile configuration hot reload
Other repositories with this package name
- deepseek-ai/deepseek-harness--packages-boot-hmr
- See-Sol-Lab/DeepSeekGUI--packages-boot-hmr
- wanghongjian0119/deepseek-harness-desktop--packages-boot-hmr
- cherrchen/Rivetdeck--packages-boot-hmr
- lihuabai629-star/deepseek-harness-openubmc--packages-boot-hmr
- Missher12/deepseek-harness-desktop--packages-boot-hmr
Install
This plugin has no verified bundle, or compatibility checks failed. Read the repository notes first. Read the full README ↗
README
Read the full README ↗Configuration
| Field | Default | Meaning |
|---|---|---|
base | Context base URL | Base directory for module watching. |
root | ["."] | Module watch roots; [] retains only explicit configuration watches. |
ignored | ["**/node_modules", "**/.*", "cache", "data"] | Excluded module paths. |
debounce | 100 | Milliseconds for combining module changes. |
Chokidar options, including polling, retain their existing meaning. Exact configuration watches also observe additions, removals and initially missing parent directories. They default to awaitWriteFinish: true: edits wait for Chokidar's 2-second write-stability window, avoiding its lossy change-event throttle. Configure awaitWriteFinish to adjust that window; disabling it can miss rapid consecutive edits. Direct Plugin Manager operations apply without waiting for file events.
Profile recompositions run by HMR's profile watches and by Plugin Manager also replace plugins whose loaded files below the profile directory changed on disk. This covers installed packages below node_modules and the targets of linked packages. A package whose files changed in place, such as a linked package whose build output changed or a dependency another installation upgraded, therefore takes effect without a restart at the next such recomposition; source watching through root is not required. A replacement that fails to load stops the previous plugin and is reported as failed with its load error instead of as a restart, which would load the same files; every later recomposition imports it again, so it starts once its files or dependencies are corrected.