Repository navigation
Run a packaged add-on without node on PATH - #9
Merged
Merged
Conversation
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
approved these changes
Nov 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.