You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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
andnodejs-wheel
packages (njzjz/nodejs-wheel#23)The text was updated successfully, but these errors were encountered: