Bun 1.3
bun.sh
Bun 1.3 introduces zero-config frontend development, unified SQL API, built-in Redis client, security enhancements, package catalogs, async stack traces, VS Code test integration, and Node.js compatibility improvements.

About Bun:

Bun is a fast, incrementally adoptable all-in-one JavaScript, TypeScript & JSX toolkit. Use individual tools like bun test or bun install in Node.js projects, or adopt the complete stack with a fast JavaScript runtime, bundler, test runner, and package manager built in. Bun aims for 100% Node.js compatibility.

1.3 release:

The highlights:

  • Full‑stack dev server (with hot reloading, browser -> terminal console logs) built into Bun.serve()
  • Builtin MySQL client, alongside our existing Postgres and SQLite clients
  • Builtin Redis client
  • Better routing, cookies, WebSockets, and HTTP ergonomics
  • Isolated installs, catalogs, minimumRelease, and more for workspaces
  • Many, many Node.js compatibility improvements
  • dogs0n@sh.itjust.works
    3·
    21 days ago

    Bun is supposed to be a drop in replacement for node and it can work like that for many apps currently as far as I know.

    So it only comes with and will come with improvements.

    At scale it could potentially save a lot of money.

    Sounds like it will help with developer experience too so… I can’t tell why you hate it.

    Personally I think deno and bun will find their space (which may overlap over a lot of space that node currently takes) and their existence is a net good.

    • Kissaki@programming.devOPEnglish
      3·
      20 days ago

      I refuse to install nodejs on my personal PC. Too big, too pervasive, not observable. These tools, Deno and Bun, allow me to work on node/js/ts projects. At least, when they are compatible, which sadly they are not always.

      • dogs0n@sh.itjust.works
        1·
        20 days ago

        I have never heard that take before, but to each their own.

        And if you prefer deno/bun, that’s great, I still think they are the future, hopefully they get closer to 100% node compatibility, I’m sure it just needs time (node spec is likely very huge by now).

        Do you work with many different projects? What’s the failure rate of deno/bun not working out the box for you (I’m curious)?

        • Kissaki@programming.devOPEnglish
          1·
          19 days ago

          At work, I don’t have to work with node projects at all.

          Outside of work, some drive-by contributions or where I contribute or would have liked to contribute. For example, on OpenTermsArchive, or the Nushell website (where it doesn’t work with their vuepress, unfortunately).