v1.1.18 causes "could not determine executable to run for package xxx"

[kouhin]

What version of Bun is running?

1.1.18+5a0b93523

What platform is your computer?

Darwin 23.5.0 arm64 arm

What steps can reproduce the bug?

Run bunx node-jq

What is the expected behavior?

Before v1.1.18

> bunx node-jq
jq - commandline JSON processor [version 1.7.1]

Usage:	/private/tmp/bunx-501-node-jq@latest/node_modules/.bin/node-jq [options] <jq filter> [file...]
	/private/tmp/bunx-501-node-jq@latest/node_modules/.bin/node-jq [options] --args <jq filter> [strings...]
	/private/tmp/bunx-501-node-jq@latest/node_modules/.bin/node-jq [options] --jsonargs <jq filter> [JSON_TEXTS...]

jq is a tool for processing JSON inputs, applying the given filter to
its JSON text inputs and producing the filter's results as JSON on
standard output.

The simplest filter is ., which copies jq's input to its output
unmodified except for formatting. For more advanced filters see
the jq(1) manpage ("man jq") and/or https://jqlang.github.io/jq/.

Example:

	$ echo '{"foo": 0}' | jq .
	{
	  "foo": 0
	}

For listing the command options, use /private/tmp/bunx-501-node-jq@latest/node_modules/.bin/node-jq --help.

What do you see instead?

After upgrading to v1.1.18

~/.bun/bin
❯ bun pm cache rm -g
Cleared 'bun install' cache
Cleared 1 cached 'bunx' packages

~/.bun/bin
❯ bunx node-jq
error: could not determine executable to run for package node-jq

Additional information

No response

[RiskyMH]

probably caused by #11886

Skips linking binaries when the target does not exist