[Bug] Cordis loader fails to import a valid ESM plugin entry point (failed to import)

[JiamingShi-JsPhys]

Environment:

• OS: Windows 11 (10.0.26200.9457)
• Client: DSH Desktop
• Plugin Repository: https://github.com/JiamingShi-JsPhys/chelate-shell

Describe the bug:
The DSH Desktop client successfully installs the plugin and displays it in the plugin list. However, every time the client starts, it throws a warning: 启用失败: dsh: warning: 1 entry did not activate chelate-shell (chelate-shell): failed to import. The plugin status remains "Not Running" (未运行).

Troubleshooting & Evidence:
To isolate the issue, I have performed the following verifications:

1. Code is Valid: Running the entry file directly via local Node.js (node .dsh-plugin/index.js) executes perfectly with zero errors.
2. Cross-Platform Compatibility: The exact same repository successfully loads all skills and works flawlessly on WorkBuddy and OpenAI Codex.
3. Format Variations Tried: I have tried both CommonJS (module.exports) and pure ESM (export function apply). Both result in the same failed to import error.
4. Dependency Cache: Tried clearing node_modules, pnpm-lock.yaml, and bumping the plugin version to force a clean reinstall. The issue persists.

Expected behavior:
The Cordis loader should successfully import the index.js file and activate the plugin on startup.

Actual behavior:
The plugin fails to import and remains inactive.

Relevant Code Snippets:

package.json:

{
  "name": "chelate-shell",
  "version": "1.0.0",
  "type": "module",
  "main": ".dsh-plugin/index.js",
  "exports": {
    ".": "./.dsh-plugin/index.js"
  },
  "files": [
    ".dsh-plugin/index.js",
    "cordis.patch.yml",
    "skills/"
  ],
  "dsh": {
    "bundle": {
      "patch": "./cordis.patch.yml"
    }
  }
}

cordis.patch.yml:

- insert:
    - id: chelate-shell
      name: chelate-shell

.dsh-plugin/index.js (Minimal reproduction):

export const name = 'chelate-shell';

export function apply(ctx) {
  console.log('[chelate-shell] Plugin mounted successfully.');
  return { status: 'active' };
}

Additional Context:
It appears there might be an issue with how the Cordis loader resolves the exports field or handles ESM syntax in Windows environments for Git-installed plugi

[barry166]

The manifest in the post does not match the repository currently being installed: the current package.json points both main and exports["."] at ./lib/index.js, but the repository has no lib/ directory. DSH imports the bundle by package name, so Node follows that installed exports target instead of looking for .dsh-plugin/index.js. Point both fields back to ./.dsh-plugin/index.js (as in the snippet), or commit the built lib/index.js, then update/reinstall the Git bundle so its local checkout gets the corrected manifest. Checking the installed copy of package.json will confirm which revision DSH is resolving.

[JiamingShi-JsPhys]

Hi Barry,

I have tried all your suggestions, but the plugin still fails to import. Here is what I've done so far:

1. Moved entry to lib/index.js: Updated package.json (main and exports) to point to lib/index.js and added "type": "module". Result: failed to import.
2. Tried pure CommonJS at root: Removed "type": "module", placed a minimal index.js at the root directory, and set "main": "index.js". Result: failed to import.

To prove the code is completely valid, I ran node index.js locally, and it executes without any errors.

This appears to be a fundamental issue with how the Cordis loader resolves modules in the Windows Desktop client, regardless of the entry point or module system used. Could you please check if there's a module resolution bug in the Windows build?

Thanks for your help.

[kirlyr]

I checked the current repo, and your root index.js and package.json now look consistent, so I don't think the old lib/index.js mismatch explains the latest failure.

One thing I'd try is bypassing the Desktop repository-plugin installation path and installing it as a regular DSH bundle:

dsh plugin --profile web add github:JiamingShi-JsPhys/chelate-shell
dsh --profile web --dump-config

The official DSH docs support this bundle installation flow, and your repo already has the dsh.bundle manifest and patch file.

If it loads this way but still fails through the Desktop plugin panel, that would point toward the repository-plugin loader rather than your entry module.

If both fail, the underlying import exception would be the next thing to inspect. The current failed to import warning hides the detail we need.