migrate to bun about pm2 HOT 6 OPEN

Won't be nice to make that as default?

I don't see any disadvantage of not using bun

from pm2.

It won't be as easy as just stating "let's make a different interpreter the default".
Here's some cons just for sake of argument:

• Bun is still under development.
• Bun is not as widely used as Node.js.
• Bun does not support all Node.js APIs.
• Bun is not as well-documented as Node.js.

So, while Node.js is still the most popular, complete and stable production-ready interpreter, in my opinion PM2 should stick with it and only start discussing about it when Node.js is surpassed in those areas.

Nothing against Bun, but you have to be realistic.

from pm2.

You want to use bun as interpreter?

pm2 start --interpreter ~/.bun/bin/bun

from pm2.

You want to use bun as interpreter?

pm2 start --interpreter ~/.bun/bin/bun

how i can make it permament and then how i can leave it as default?

from pm2.

Actually coming back to this, it seems that bun is the default already for typescript (bad decision if you ask me) since oct 6 2023:
135c123

That would mean that if you really want to use bun by default, either modify that file manually or use typescript extension.

from pm2.

I can't get pm2 to work with bun at all. Whatever I do pm2 always gives this error:

/usr/bin/env: 'node': No such file or directory

I have tried with command line arguments and with a configuration file. Still it seems to ignore the interpreter argument completely.

.bun/bin/pm2 start ecosystem.json
.bun/bin/pm2 start --interpreter bun index.js
.bun/bin/pm2 start --interpreter /usr/local/bin/bun index.js

ecosystem.json:

{
  "apps": [
    {
      "name": "myapp",
      "script": "index.js",
      "interpreter": "/usr/local/bin/bun",
      "instances": 1,
      "exec_mode": "fork",
      "autorestart": true,
      "watch": false,
      "error_file": "./errors.log",
      "out_file": "./myapp.log"
    }
  ]
}

from pm2.