runline 0.7.5
Fixed
External workspace plugins can now import Runline's public API without needing a local node_modules directory next to the plugin file.
This fixes hosted/plugin-directory setups where a plugin lives outside the app package tree and follows the documented authoring pattern:
import type { RunlinePluginAPI } from "runline";
import { commandExists } from "runline";
import { syncExec } from "runline/utils/cli";loadPluginFromPath() now loads plugins through a Runline-owned jiti context, with aliases for runline and runline/utils/cli. That keeps plugin DX simple while avoiding fragile package resolution from arbitrary workspace paths.
Verified
- Biome check passes
- Build passes
- Runline test suite passes: 107 tests
- New regression coverage for external plugin files importing both
runlineand public subpaths
Full Changelog: v0.7.4...v0.7.5