Package Details: bun-bin 1.3.4-1

Git Clone URL: https://aur.archlinux.org/bun-bin.git (read-only, click to copy)
Package Base: bun-bin
Description: All-in-one JavaScript runtime built for speed, with bundler, transpiler, test runner, and package manager. Includes bunx, shell completions and support for baseline CPUs
Upstream URL: https://github.com/oven-sh/bun
Keywords: bun javascript npm
Licenses: MIT
Conflicts: bun
Provides: bun
Submitter: thdxr
Maintainer: NoelJacob
Last Packager: NoelJacob
Votes: 98
Popularity: 4.76
First Submitted: 2022-07-06 01:57 (UTC)
Last Updated: 2025-12-07 05:01 (UTC)

Dependencies (0)

Required by (60)

Sources (3)

Latest Comments

1 2 3 4 5 6 Next › Last »

marmis commented on 2025-10-31 02:30 (UTC)

Hi, @NoelJacob. I have ~/.local/bin as part of my $PATH, and I noticed that bun creates a symlink to ${srcdir} during the first install of this package:

> ls -l ~/.local/bin/bunx
lrwxrwxrwx 1 marmis marmis 42 out 30 22:35 /home/marmis/.local/bin/bunx -> /tmp/makepkg/bun-bin/src/bun-linux-x64/bun

It seems that this is done in bunx_command.zig, which creates a bunx symlink in the first item of $PATH if no bunx is found.

I think a good workaround for this is prepend ${srcdir} to PATH right before creating the completions. Somethign like this:

    install -dm755 "completions"
    export PATH="${PWD}:${PATH}"
    SHELL=zsh "./bun" completions >"completions/bun.zsh"
    SHELL=bash "./bun" completions >"completions/bun.bash"
    SHELL=fish "./bun" completions >"completions/bun.fish"

I tested after uninstalling bun and clearing all bunx symlinks, and this does indeed work. It creates the temporary symlink under ${srcdir}/bun-linux-x64.

douglasduteil commented on 2025-10-15 09:48 (UTC)

1.3.0 is out 🎉. https://github.com/oven-sh/bun/releases/tag/bun-v1.3.0

BestCodes commented on 2025-05-29 01:24 (UTC)

1.2.5 is out. https://github.com/oven-sh/bun/releases/tag/bun-v1.2.15

iiiypuk commented on 2025-02-27 16:50 (UTC)

bun, javascript,

Error comma characters in tags

NoelJacob commented on 2024-03-05 06:09 (UTC)

It's all good now @rnbguy

rnbguy commented on 2024-02-26 12:28 (UTC) (edited on 2024-02-26 12:29 (UTC) by rnbguy)

You can maintain LICENSE separately if this makes it easier.

sha256sums=("002c2696d92b5c8cf956c11072baa58eaf9f6ade995c031ea635c6a1ee342ad1")
source=("LICENSE")
sha256sums_x86_64=(...)
source_x86_64=(...)
sha256sums_aarch64=(...)
source_aarch64=(...)

MathMan05 commented on 2024-02-20 02:33 (UTC)

It's broken, the PKGBUILD really messed up and has a big error with an extra ")" in the middle of the hashes

AsukaMinato commented on 2024-02-20 00:25 (UTC) (edited on 2024-02-20 00:26 (UTC) by AsukaMinato)

after update, run this command

shfmt -w PKGBUILD && updpkgsums && makepkg --printsrcinfo > .SRCINFO && makepkg  -C -sf && namcap *.zst

which will erase many problems.

dchusovitin commented on 2024-02-19 23:46 (UTC)

Syntax error in the PKGBUILD file (sha256sums_* sections), an extra parenthesis

bun-bin/PKGBUILD: line 15: 002c2696d92b5c8cf956c11072baa58eaf9f6ade995c031ea635c6a1ee342ad1: command not found bun-bin/PKGBUILD: line 16: syntax error near unexpected token `)' bun-bin/PKGBUILD: line 16: `)'

1 2 3 4 5 6 Next › Last »