Switch from Bun to Deno

[timrogers]

No description provided.

[Jarred-Sumner]

Sorry to see this. Is there anything we (Bun) could've done differently? Were there any bugs or issues you ran into?

[timrogers]

@Jarred-Sumner Thanks for reaching out - I appreciate the white glove support ❤️

I really loved the experience of switching from Node to Bun - it was so easy to get started, bun build --compile is a 👨🏻‍🍳 😽 idea and bun patch made it easy to get my dependencies working.

The issue that I hit was that my macOS binaries, built with this workflow, didn't work properly after signing with my Apple developer account. Instead, they behaved as a Bun interpreter:

$ ./gh-migrate-project-darwin-arm64
Bun is a fast JavaScript runtime, package manager, bundler, and test runner. (1.2.0+b0c5a7655)

Usage: bun <command> [...flags] [...args]

Commands:
  run       ./my-script.ts       Execute a file with Bun
            lint                 Run a package.json script
  test                           Run unit tests with Bun
  x         prettier             Execute a package binary (CLI), installing if needed (bunx)
  repl                           Start a REPL session with Bun
  exec                           Run a shell script directly with Bun

  install                        Install dependencies for a package.json (bun i)
  add       @evan/duckdb         Add a dependency to package.json (bun a)
  remove    redux                Remove a dependency from package.json (bun rm)
  update    @zarfjs/zarf         Update outdated dependencies
  outdated                       Display latest versions of outdated dependencies
  link      [<package>]          Register or link a local npm package
  unlink                         Unregister a local npm package
  publish                        Publish a package to the npm registry
  patch <pkg>                    Prepare a package for patching
  pm <subcommand>                Additional package management utilities

  build     ./a.ts ./b.jsx       Bundle TypeScript & JavaScript into a single file

  init                           Start an empty Bun project from a blank template
  create    vite                 Create a new project from a template (bun c)
  upgrade                        Upgrade to latest version of Bun.
  <command> --help               Print help text for command.

Learn more about Bun:            https://bun.sh/docs
Join our Discord community:      https://bun.sh/discord

Is that a known issue?

[timrogers]

If I follow exactly the same build process, without the signing step, I get a binary that works as expected, but then you hit the issue of macOS requiring ARM64 binaries to be signed.

[timrogers]

@Jarred-Sumner I'd love to get your take on this if you have a chance!