v1.7.1

aubeshim 1.7.1 fixes bun run for targets that are files, directories, or commands instead of package.json scripts.

bun run <target> falls back to real Bun for non-script targets

Bun resolves a bun run target as a package.json script first, then as a source file (adding extensions and index.*), a package bin, or a system command. aubeshim used to route every bare target to aube run, which only knows scripts and bins, so commands like these failed with script not found:

• bun run scripts/export, where scripts/export/ holds an index.ts
• bun run scripts/build, where only scripts/build.ts exists
• bun run ls

bun run <target> now goes to the real Bun binary whenever <target> is not a script in the nearest package.json. Script names still run through aube, including names that also exist as a directory, and bun run --filter <pkg> <script> stays on aube.

Thanks to @tommy-gilligan for reporting this and proposing the first fix in #3.

Full Changelog: v1.7.0...v1.7.1