DSH Market
D

Dsh Super Injector

by yjh051108 · yjh051108/dsh-super-injector

Build failsBundlegit (build fails)fresh

No description provided.

Install Dsh Super Injector

Likely fails to load: not on npm, needs a build, and ships no `prepare` script — a git install fetches sources, not built artifacts, so the entry point is never produced.

This install is expected to fail

A git install pulls source, not build output. This package needs a build step, has no prepare script to run it, and is not published to npm — so nothing produces the compiled output the loader then goes looking for.

Three things would fix it, all of them on the author's side: publish the package to npm, add a prepare script that builds on install, or commit the build output to the repository. Until one of those happens, the command below is here so you can reproduce the failure, not so you can install it.

What would be run — expected to install and then fail to load

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:yjh051108/dsh-super-injector

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Before you run it

  • A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
  • Installing from git resolves a moving branch. Pin a commit — github:yjh051108/dsh-super-injector#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key
Not required.
Network access
Not required at runtime.
Language
TypeScript — a git install pulls this source, not build output.

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
dsh.bundlepassfatalpackage.json declares a `dsh.bundle` layer
dsh.bundle.patch filepassfatalpatch file present at `cordis.patch.yml`
npm registrymissingwarn`@dsh-external/dsh-super-injector` is not published to npm
prepare scriptmissingfatalneeds a build but ships no `prepare` script — a git install fetches sources, not built artifacts
Verdict reason
git-only + needs build + no prepare script
package.json read
package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

> ## 🎉 v0.3.0 重大声明(2026-08-14) > > **从经验补丁到源码契约——注入器完成规范重构。** > > 本版本按 [docs/SPEC.md](./docs/SPEC.md)(基于 DSH 0.1.0-rc.6 源码语义推导的 > 设计契约)重构自重载为**官方 REPLACE 结构**:工具只排程、绝不亲自自杀; > reboot 走 `entry._dispose`(官方 `_disposing` 豁免)+ 失败自动 rollback。 > 从此注入器的一切行为都有源码依据,不再依赖经验补丁。 > > **里程碑回顾**: > - 三轮零上下文 subagent 评测:9/10 → 9.5/10 → **10/10** > - 作死压力测试:连环自杀/坏语法/悬空 junction/循环注入卸载——**零崩溃零残留** > - **云源自举**:下载 release 副本 → 装配 → 注入器从云端副本运行(自检 8/8) > - **免杀进程恢复**:失败 → touch patch(include.refresh 进程内重装配)→ 6 秒复活 > - **DSH 正式版兼容**:0.1.0-rc.6 一行不改直接运行(peerDeps 范围声明实证) > > 哲学不变:**一切皆插件**——注入器是 DSH 生态的运行时注入标准层, > 让"插件想长成什么样就长成什么样"。 DSH 生态的 **BepInEx 式模组注入入口**:运行时把任意本地插件包注入运行中的 web, 不碰 patch / package.json / bundles 列表、不重启进程。**注入即完整生效(host 工具 + client UI)。** > 灵感:官方装配机制(profile bundle / repository-plugin)是唯一的"官方入口

Topics

GitHub topics on this repository

Related entries

Nearest entries by similarity — this one landed in no themed cluster