Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

separate package for only the binaries without the CLI #2

Closed
DetachHead opened this issue Oct 7, 2024 · 1 comment · Fixed by #3
Closed

separate package for only the binaries without the CLI #2

DetachHead opened this issue Oct 7, 2024 · 1 comment · Fixed by #3
Assignees
Labels
enhancement New feature or request

Comments

@DetachHead
Copy link

if i'm publishing a package that depends on bun, i don't want the CLI to be available because i don't want the user to unknowingly have a bun executable added to their PATH. instead i only want the binaries to be accessible programmatically.

for example the nodejs-wheel project publishes separate nodejs-wheel-binaries and nodejs-wheel packages (njzjz/nodejs-wheel#23)

@ducdetronquito ducdetronquito added the enhancement New feature or request label Oct 7, 2024
@ducdetronquito ducdetronquito self-assigned this Oct 7, 2024
@ducdetronquito
Copy link
Owner

Hi again @DetachHead !

Thanks for your feedback, I will look into it too !

ducdetronquito added a commit that referenced this issue Oct 7, 2024
We silently expose a CLI to the bun executable on the user's PATH
which could mess with its own existing bun setup.

Instead, pybun now only exposes a CLI to the bun executable via `pybun`,
`python -m pybun`, or a programmatic access.

---

Fix #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants