Fix global tsci install requiring Bun at runtime#3318
Open
mohan-bee wants to merge 4 commits into
Open
Conversation
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
1 participant
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.
Fixes tscircuit/tscircuit#2828
This fixes tsci failing after npm install -g tscircuit on machines without Bun installed.
Previously, the CLI entrypoint selected bun or tsx to run the built CLI. That meant a globally installed tsci command could still fail with:
env: bun: No such file or directoryThe entrypoint now runs the built CLI with the current Node executable using process.execPath, so npm global installs only require Node at runtime.
Motivation
Users installing with npm should not need to install Bun separately just to run tsci.