[Bug]: file:// plugin dedup silently drops plugins when multiple share the same filename (e.g. index.js)

[Aegis-commits]

Description

When two or more plugins are loaded via file:// paths and their JS filenames are identical (e.g. both named index.js), deduplicatePlugins() silently drops all but one. No error or warning is logged.

Reproduction

// opencode.json
{
  "plugin": [
    "file:///home/user/plugin-a/dist/index.js",
    "file:///home/user/plugin-b/dist/index.js"
  ]
}

Expected: Both plugins load.
Actual: Only one loads (the later entry wins). The other is silently discarded.

Root Cause

getPluginName() extracts just the bare filename (without extension) for file:// URLs. Both paths resolve to canonical name "index". deduplicatePlugins() then treats them as the same plugin and keeps only the last one (reverse-order processing, last = highest priority).

Impact

This is a silent failure — no error, no warning, no log entry. The dropped plugin simply doesn't exist at runtime. This is especially likely during local plugin development where dist/index.js is the standard build output for most bundlers (bun, esbuild, rollup, etc.).

Suggested Fix

For file:// URLs, derive the canonical name from a more unique portion of the path rather than just the bare filename. Options:

1. Use the parent directory name + filename (e.g. plugin-a/index → "plugin-a")
2. Use the full path as the canonical name for file:// entries
3. At minimum, log a warning when dedup discards a file:// plugin

Workaround

Ensure each file:// plugin has a unique JS filename:

ln -sf /path/to/plugin/dist/index.js /path/to/plugin/dist/my-plugin.js

{
  "plugin": [
    "file:///home/user/plugin-a/dist/plugin-a.js",
    "file:///home/user/plugin-b/dist/index.js"
  ]
}

Environment

• OpenCode (latest)
• Linux x86_64
• Multiple file:// plugins in config

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Bug: file:// plugins with same filename incorrectly deduplicated #8759: Bug: file:// plugins with same filename incorrectly deduplicated
• Plugin deduplication incorrectly removes plugins with index.js entry points #11159: Plugin deduplication incorrectly removes plugins with index.js entry points
• Bug: getPluginName incorrectly deduplicates plugins with same entry filename (index.js) #12285: Bug: getPluginName incorrectly deduplicates plugins with same entry filename (index.js)
• [Bug]: Only the last plugin loads in OpenCode 1.1.32 - Multiple plugins not supported #10115: Only the last plugin loads - Multiple plugins not supported

Please review these issues before continuing, and consider adding your findings there if they match your case.

[cyberprophet]

This is addressed by #15598 which adds node_modules-aware path parsing to getPluginName(). CI is green.

The root cause is that import.meta.resolve resolves npm plugins to file://…/node_modules/<pkg>/dist/index.js, and then getPluginName() extracts only the filename "index", causing false collisions with any project plugin that also has an index.ts entry point.

Related issues: #8759, #10115, #11159, #12285, #14304, #15591