| Git Clone URL: | https://aur.archlinux.org/bun.git (read-only, click to copy) |
|---|---|
| Package Base: | bun |
| Description: | Bun is a fast JavaScript all-in-one toolkit. This PKGBUILD builds from source, resulting into a smaller and faster binary depending on your CPU. |
| Upstream URL: | https://github.com/oven-sh/bun |
| Keywords: | bun compile js node ts |
| Licenses: | GPL |
| Conflicts: | bun-bin |
| Submitter: | tiziodcaio |
| Maintainer: | tiziodcaio |
| Last Packager: | tiziodcaio |
| Votes: | 12 |
| Popularity: | 3.08 |
| First Submitted: | 2023-09-12 21:31 (UTC) |
| Last Updated: | 2024-04-12 19:04 (UTC) |
Based on the Rust packaging guidelines, this should have export RUSTUP_TOOLCHAIN=stable in the prepare() and build() steps, at least while Bun is still in the AUR.
I'd also recommend running a shellcheck over the PKGBUILD, ignoring errors about unexported variables. There's a few unquoted strings that rua's shellcheck wrapper is complaining about.
Having some problems while building 1.0.33:
clang: error: invalid linker name in argument '-fuse-ld=lld'
The fix is to have the latest lld as well (in addition to lld16).
Sadly is not an issue... You can use bun-bin if you have not built yet. If you prefer a cleaner workflow, I can think about pulling a release of bun as a source, so then I can use that version to bring you the source-compiled version.
Also confirming the same issue on my end, where bun is needed to install bun. Thankfully bin-bin works well enough for me for now as an alternative.
Clean chroot. Impossible to build because tries to run itself before it is even built.
==> Starting prepare()...
/home/main-builder/pkgwork/PKGBUILD: line 19: bun: command not found
Clean chroot. Impossible to build/install because depends on itself.
error: target not found: bun
@jcaesar at the moment you should install bun or npm, you can chose... But while you upgrade it should be better use directly bun... So it shouldn't be added the dependency to npm imo
I'm working on it... sorry but atm please be patient
I suppose the fact that this depends on bun itself can be worked around by first installing bun-bin. Still, I'm not able to build, it fails with
✘ [ERROR] Could not resolve "peechy"
src/fallback.ts:2:27:
2 │ import { ByteBuffer } from "peechy";
╵ ~~~~~~~~
You can mark the path "peechy" as external to exclude it from the bundle, which will remove this error.
1 error
make: *** [Makefile:832: fallback_decoder] Error 1
Pinned Comments
tiziodcaio commented on 2023-12-13 15:15 (UTC)
Sadly is not an issue... You can use
bun-binif you have not built yet. If you prefer a cleaner workflow, I can think about pulling a release of bun as a source, so then I can use that version to bring you the source-compiled version.xiota commented on 2023-11-09 12:14 (UTC)
Clean chroot. Impossible to build/install because depends on itself.