Pi installed with bun is using node under the hood

[remixer-dec]

What happened?

After seeing a message that Node 20 is no longer supported I decided to uninstall and reinstall pi with bun.

However this causes

~/.bun/install/global/node_modules/undici/lib/web/cache/cachestorage.js:20
    webidl.util.markAsUncloneable(this)
                ^

TypeError: webidl.util.markAsUncloneable is not a function

becuase pi executable is still using
#!/usr/bin/env node
despite being installed in ~/.bun/bin/pi

suggested fix:
use #!/usr/bin/env bun for bun installations

Steps to reproduce

Expected behavior

No response

Version

No response

[github-actions]

This issue was auto-closed. All issues from new contributors are auto-closed by default.

Maintainers review auto-closed issues daily and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md will not be reopened or receive a reply.

If a maintainer replies lgtmi on one of your issues, your future issues will stay open. If a maintainer replies lgtm, your future issues and PRs will stay open.

See CONTRIBUTING.md.

[badlogic]

the pi executable can't know that you are using bun. this shebang is baked into the entry point script. you can manually modify it, or create an alias.

[joaomoreno]

I just hit this. This is pretty bad UX. The homepage clearly points at this "just working":

Yet:

ubuntu@feasible-jabiru:~$ bun add -g --ignore-scripts @earendil-works/pi-coding-agent
bun add v1.3.14 (0d9b296a)

installed @earendil-works/pi-coding-agent@0.80.6 with binaries:
 - pi

127 packages installed [1.98s]

Blocked 2 postinstalls. Run `bun pm -g untrusted` for details.
ubuntu@feasible-jabiru:~$ pi
env: 'node': No such file or directory
env: use -[v]S to pass options in shebang lines

You could (1) remember the execution preference depending on the install script used and (2) write a dynamic shell script that picks that preference first, defaulting to the other supported runtimes if not available.