fusion/.changeset/workflow-graph-editor-and-bundled-plugins.md at 4ffd0a2ddef2effbb9ca839c3136540d182eebe6

Files

gsxdsm 4426eb8d74 Fix Settings plugin installs registering unloadable directory paths

Plugins installed from Settings → Built-in Plugins registered the
manifest directory as the plugin path, but since FN-4128 the loader
requires a loadable entry FILE (Node ESM cannot import directories),
so enabling failed with "Plugin entry must be a file, got directory".
Only the CLI startup path had been migrated to entry-file resolution,
which is why CLI-auto-installed plugins worked and Settings installs
never did.

- Add resolvePluginEntryPath (bundled.js → dist/index.js →
  src/index.ts) to @fusion/core; the CLI keeps its local copy (its
  test fs mocks don't reach externalized core) with sync comments
  both ways.
- Register the resolved entry file in both dashboard install routes;
  400 with a clear message when a package has no loadable entry.
- Heal legacy directory-path registrations on enable, mirroring the
  CLI's startup heal, so existing broken rows recover from the UI
  without a restart.
- Route tests: assert installs register entry files, cover the
  enable-route heal, and update existing install tests to the
  entry-file contract.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-04 21:57:46 -07:00

1.2 KiB

Raw Blame History

@runfusion/fusion

@runfusion/fusion
patch

Fix the workflow graph editor opening invisibly and bundle the Compound Engineering and Roadmaps plugins.

The "Graph editor" button now actually shows the editor: its overlay was rendered without the open class, leaving it display: none, so opening it looked like the workflow steps view was just dismissed.
fusion-plugin-compound-engineering and fusion-plugin-roadmap are now listed in the dashboard's built-in plugins, so they appear under Settings → Built-in Plugins (they were implemented and registered but missing from the list).
Installing Compound Engineering (and CLI Printing Press) from Settings → Built-in Plugins no longer fails with "Plugin manifest not found": both ids are now in the dashboard's bundled-plugin fallback set, and the Compound Engineering plugin is staged into dist/plugins/ so packaged installs can resolve it.
Plugins installed from Settings now load instead of erroring with "Plugin entry must be a file, got directory": the dashboard install routes register the plugin's loadable entry file (bundled.js/dist/index.js/src/index.ts) rather than the package directory, and enabling a plugin heals legacy directory-path registrations in place.

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History