Package Details: bun 1.2.12-1

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, bun-git
Submitter: tiziodcaio
Maintainer: tiziodcaio
Last Packager: tiziodcaio
Votes: 20
Popularity: 1.28
First Submitted: 2023-09-12 21:31 (UTC)
Last Updated: 2025-05-04 21:08 (UTC)

Pinned Comments

tiziodcaio commented on 2025-03-03 11:05 (UTC)

If you have got killed signal it means that you do not have enough RAM to compile it.

tiziodcaio commented on 2025-01-31 09:42 (UTC)

Due to some complains I'll open a copy of the repository on github to get a better ticket system. If you have any issue with bun's packaging, you can also contact me on

https://github.com/tiziodcaio/bun/issues

or you can make a PR to https://github.com/tiziodcaio/bun/pulls

tiziodcaio commented on 2025-01-31 06:42 (UTC)

I need help packaging. Anyone could help as comantainer?

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

yegorius commented on 2024-03-20 15:17 (UTC) (edited on 2024-03-22 16:12 (UTC) by yegorius)

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).

tiziodcaio commented on 2023-12-13 15:15 (UTC)

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.

hak8or commented on 2023-12-09 15:12 (UTC)

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.

xiota commented on 2023-11-29 06:57 (UTC)

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

xiota commented on 2023-11-09 12:14 (UTC)

Clean chroot. Impossible to build/install because depends on itself.

error: target not found: bun

tiziodcaio commented on 2023-09-14 11:01 (UTC)

@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

tiziodcaio commented on 2023-09-14 10:49 (UTC)

I'm working on it... sorry but atm please be patient

jcaesar commented on 2023-09-14 02:30 (UTC)

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

aorth commented on 2023-09-13 08:02 (UTC) (edited on 2023-09-13 08:02 (UTC) by aorth)

There seem to be build issues here:

  • Packages provide themselves, so no need to provide=(bun)
  • Packages don't need to explicitly conflict with themselves, so you can remove conflicts=(bun)
  • You can add conflicts=(bun-bin)
  • As @MarsSeed mentioned, no need to use replaces=(bun-bin)

Even so, I still fail to build this package. I think it's because the prepare step is calling bun but we don't have bun installed yet. :P It's a good idea to build these packages in a clean chroot with aurutils so you can see these build issues.

« First ‹ Previous 1 2 3 4 Next › Last »