Use bun as a task executor #477

Activity

1. seveibar commented on Jun 18, 2024

   

   seveibar

   on Jun 18, 2024

   Last edited by seveibar

   Author

   More actions

   This is possible by running bunx --bun graphile-worker .... The --bun flag essentially replaces internal calls to node. It's a pretty simple solution. I can test it out for a couple days just to make sure it's not a totally broken way to do it, then can PR documentation for it (assuming that's ok w/ @benjie)

   

   👍React with 👍1Reacted by Peter Sugihara
2. benjie commented on Jul 1, 2024

   

   benjie

   on Jul 1, 2024

   Last edited by benjie

   Member

   More actions

   I think adding something to the docs saying something along the line of the following would be good 👍

   While bun is not an officially supported runtime for Graphile Worker, users have reported success when executing bunx --bun graphile-worker. The --bun is necessary to ensure that child processes also run using bun rather than node.

   👍React with 👍3Reacted by Severin Ibarluzea, Peter Sugihara and Nova
3. andrioid commented on Jan 12, 2025

   

   andrioid

   on Jan 12, 2025

   More actions

   I have a worker/index.ts file that runs the runner from a bun index.ts package.json script.

   import { run } from "graphile-worker";
   import preset from "./graphile.config";
   
   async function main() {
     const runner = await run({ preset });
     await runner.promise;
   }
   
   main().catch((err) => {
     console.error(err);
     process.exit(1);
   });

   It works well, and cuts through a lot of the TypeScript packaging pain points. However, I am noticing memory leaks that I suspect have something to do with Bun. So, use at your own risk 😄

   👍React with 👍2Reacted by Alistair Roche and Dominik Nussbaumer
4. benjie

   added

   enhancementNew feature or requestNew feature or request

   on Jul 29, 2025