Skip to content

Run a packaged add-on without node on PATH - #9

Merged
colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:fix-bundled-runtime
Nov 14, 2026
Merged

colinjlacy merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:fix-bundled-runtime

Conversation

@itvi-1234

Copy link
Copy Markdown
Member

rc refused to run the TypeScript profiler unless node was on PATH. The profiler's deb and rpm carry their own Node.js runtime, so on a machine with only the system package, rc reported runtime-missing for an add-on that runs fine.

rc no longer checks for the runtime before it runs the add-on. It asks the add-on for its version first, and only when that fails and the runtime is not on PATH does it say that the runtime is needed. With the runtime present, the real error shows. rc plugins list applies the same rule.

rc refused to run the TypeScript profiler unless node was on PATH. The profiler's
deb and rpm carry their own Node.js runtime, so on a machine with only the system
package, rc reported runtime-missing for an add-on that runs fine.

rc no longer checks for the runtime before it runs the add-on. It asks the add-on
for its version first, and only when that fails and the runtime is not on PATH does
it say that the runtime is needed. With the runtime present, the real error shows.
rc plugins list applies the same rule.
@colinjlacy
colinjlacy merged commit 95fff91 into runtimeconditions:main Nov 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants