4 ms·

The speed increases are nothing to sneeze at; I've moved a few Vite projects over to Bun and even without specific optimizations it's still noticeably faster.

by Osmose 3y ago

The speed increases are nothing to sneeze at; I've moved a few Vite projects over to Bun and even without specific optimizations it's still noticeably faster. A specific use case where Bun beat the pants out of Node for me was making a standalone executable. Node has a very VERY in-development API for this that requires a lot of work and doesn't support much, and all the other options (pkg, NEXE, ncc, nodejs-static) are out-of-date, unmaintained, support a single OS, etc. `bun build --compile` worked out-of-the-box for me, with the caveat of not supporting native node libraries at the time—this 1.1 release fixes that issue.

llimllib 3y ago
I've hit significant failures every time I've tried to use `bun build --compile`; the most recent code I was trying to compile hit this one[1]. I documented how to build a binary from a JS app with node, deno, and bun here [2]. Node SEA is a bad DX, but not that complex once you figure it out. 1: https://github.com/oven-sh/bun/issues/6832 https://github.com/oven-sh/bun/issues/6832 2: https://github.com/llimllib/node-esbuild-executable https://github.com/llimllib/node-esbuild-executable
- Jarred 3y ago
  I’m pretty sure issue #6842 was fixed in Bun v1.0.32 or so and we forgot to mark the issue as fixed Will check once I get to my computer Edit: was not fixed. We made other changes to fs.readSync to improve Node compatibility, but missed this. It will get fixed though
throwitaway1123 3y ago
Bun's standalone executables are great, but as far as I'm aware unlike Deno and Node there's no cross compilation support, and Node supports more CPU/OS combinations than either Deno or Bun. Node supports less common platforms like Windows ARM for example (which will become more important once the new Snapdragon X Elite laptops start rearing their heads [1]). [1] https://www.youtube.com/watch?v=uWH2rHYNj3c https://www.youtube.com/watch?v=uWH2rHYNj3c
- Jarred 3y ago
  We'll add cross-compilation support and Windows arm64 eventually. I don't expect much difficulty from Windows ARM once we figure out how to get JSC to compile on that platform. We support Linux ARM64 and macOS arm64.
  - galaxyLogic 3y ago
    Does it support building an EXE with all source-code removed?

by Osmose 3y ago

llimllib 3y ago

I've hit significant failures every time I've tried to use `bun build --compile`; the most recent code I was trying to compile hit this one[1]. I documented how to build a binary from a JS app with node, deno, and bun here [2]. Node SEA is a bad DX, but not that complex once you figure it out. 1: https://github.com/oven-sh/bun/issues/6832 https://github.com/oven-sh/bun/issues/6832 2: https://github.com/llimllib/node-esbuild-executable https://github.com/llimllib/node-esbuild-executable

Jarred 3y ago
I’m pretty sure issue #6842 was fixed in Bun v1.0.32 or so and we forgot to mark the issue as fixed Will check once I get to my computer Edit: was not fixed. We made other changes to fs.readSync to improve Node compatibility, but missed this. It will get fixed though

throwitaway1123 3y ago

Bun's standalone executables are great, but as far as I'm aware unlike Deno and Node there's no cross compilation support, and Node supports more CPU/OS combinations than either Deno or Bun. Node supports less common platforms like Windows ARM for example (which will become more important once the new Snapdragon X Elite laptops start rearing their heads [1]). [1] https://www.youtube.com/watch?v=uWH2rHYNj3c https://www.youtube.com/watch?v=uWH2rHYNj3c

Jarred 3y ago
We'll add cross-compilation support and Windows arm64 eventually. I don't expect much difficulty from Windows ARM once we figure out how to get JSC to compile on that platform. We support Linux ARM64 and macOS arm64.
- galaxyLogic 3y ago
  Does it support building an EXE with all source-code removed?