Package Details: bun 1.1.8-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
Submitter: tiziodcaio
Maintainer: tiziodcaio
Last Packager: tiziodcaio
Votes: 12
Popularity: 2.05
First Submitted: 2023-09-12 21:31 (UTC)
Last Updated: 2024-05-18 10:41 (UTC)

Pinned Comments

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.

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

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

error: target not found: bun

Latest Comments

« First ‹ Previous 1 2

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.

MarsSeed commented on 2023-09-12 22:16 (UTC)

Please remove replaces=(bun-bin). That package has its own legitimate basis for existence.