You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[dsh-plugin.org | dsh-plugin-hub] plugin distribution incomplete: loopx-project/loopx #5530
Cause: plugin distribution is incomplete — the entry file declared in package.json is missing from the published package (github tarball or npm package); please commit build output or publish a complete package
The log identifies the repository root (loopx-repository), rather than the DSH plugin package. At the inspected revision, the root manifest is private and declares neither main nor exports; there is no root index.js. The git-root fallback therefore selects the wrong package. Adding a root index.js or committing build output there would not install the actual plugin.
The plugin is packages/dsh-loopx-plugin, with main: ./lib/index.js, explicit exports, a build-on-pack script, and the DSH bundle patch. Its installation guide uses a prebuilt release tarball, or ./install.sh from that package directory for the source build. The marketplace entry already points to the nested plugin and the beta.5 tarball. I downloaded that release asset and confirmed it contains package/lib/index.js (SHA-256 7c5e1dca17f6ab71b4e7ad95862aa86857ff0ef31291d6a1d85c0951cf07e33b). The reported hub fallback should retain the actual plugin/artifact target instead of installing the monorepo root.
There is also a separate version mismatch: this report uses DSH 0.2.0-rc.2, while the current beta.6 source plugin explicitly declares >=0.1.5-rc.1 <0.2.0-0. The released beta.5 artifact declares >=0.1.0-rc.7 <0.1.1 || >=0.1.1-rc.1 <0.2.0-0; it also excludes DSH 0.2. The README distinguishes the prebuilt release's original compatibility from the current source build. Correcting the install target alone does not establish DSH 0.2 compatibility; that needs a separately validated plugin release or an explicitly supported DSH version.
I checked the manifests and release archive, and reproduced the root module-resolution failure with Node; I have not reproduced the original Linux hub installation or validated DSH 0.2 behavior.
The reported loopx-repository missing index.js comes from installing the monorepo root as a plugin. The independently versioned provider is dsh-loopx-plugin; its published prebuilt tgz is the correct package. Do not replace this with a root Git install or require an npm account for the released GitHub channel.
Published beta.6 and illustrated upgrade/recovery guide are available. The immutable GitHub tgz includes the compiled Host, Client, Driver and initializer; downloaded bytes match the tagged build. Native DSH 0.2 URL installation, compatible beta.5-to-beta.6 CLI upgrade/removal, offline plugin-tgz install/removal and real macOS browser Start/Pause with released CLI 1.2.4 were qualified.
The live catalog still selects beta.5. Catalog #6633 and Hub #98 need upstream adoption/release before claiming full market recovery. Released Hub 1.4.14 supports GitHub packages without publishing LoopX on npm. Windows desktop full-journey acceptance remains open under #5208.
Native browser hot uninstall failed (Web disconnected, package dependency retained); the tested recovery is to close DSH, use native CLI removal, then restart. This differs from the passing CLI/backend removal paths. Keeping the report open while the relevant upstream/platform journey remains incomplete.
Activity
Dante-dan commentedon Oct 3, 2026
The log identifies the repository root (
loopx-repository), rather than the DSH plugin package. At the inspected revision, the root manifest is private and declares neithermainnorexports; there is no rootindex.js. The git-root fallback therefore selects the wrong package. Adding a rootindex.jsor committing build output there would not install the actual plugin.The plugin is
packages/dsh-loopx-plugin, withmain: ./lib/index.js, explicit exports, a build-on-pack script, and the DSH bundle patch. Its installation guide uses a prebuilt release tarball, or./install.shfrom that package directory for the source build. The marketplace entry already points to the nested plugin and the beta.5 tarball. I downloaded that release asset and confirmed it containspackage/lib/index.js(SHA-2567c5e1dca17f6ab71b4e7ad95862aa86857ff0ef31291d6a1d85c0951cf07e33b). The reported hub fallback should retain the actual plugin/artifact target instead of installing the monorepo root.There is also a separate version mismatch: this report uses DSH
0.2.0-rc.2, while the current beta.6 source plugin explicitly declares>=0.1.5-rc.1 <0.2.0-0. The released beta.5 artifact declares>=0.1.0-rc.7 <0.1.1 || >=0.1.1-rc.1 <0.2.0-0; it also excludes DSH 0.2. The README distinguishes the prebuilt release's original compatibility from the current source build. Correcting the install target alone does not establish DSH 0.2 compatibility; that needs a separately validated plugin release or an explicitly supported DSH version.I checked the manifests and release archive, and reproduced the root module-resolution failure with Node; I have not reproduced the original Linux hub installation or validated DSH 0.2 behavior.
loopx-agent commentedon Oct 5, 2026
The reported
loopx-repositorymissingindex.jscomes from installing the monorepo root as a plugin. The independently versioned provider isdsh-loopx-plugin; its published prebuilt tgz is the correct package. Do not replace this with a root Git install or require an npm account for the released GitHub channel.Published beta.6 and illustrated upgrade/recovery guide are available. The immutable GitHub tgz includes the compiled Host, Client, Driver and initializer; downloaded bytes match the tagged build. Native DSH 0.2 URL installation, compatible beta.5-to-beta.6 CLI upgrade/removal, offline plugin-tgz install/removal and real macOS browser Start/Pause with released CLI 1.2.4 were qualified.
The live catalog still selects beta.5. Catalog #6633 and Hub #98 need upstream adoption/release before claiming full market recovery. Released Hub 1.4.14 supports GitHub packages without publishing LoopX on npm. Windows desktop full-journey acceptance remains open under #5208.
Native browser hot uninstall failed (Web disconnected, package dependency retained); the tested recovery is to close DSH, use native CLI removal, then restart. This differs from the passing CLI/backend removal paths. Keeping the report open while the relevant upstream/platform journey remains incomplete.