New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate to bun #5774
Comments
You want to use bun as interpreter?
|
Won't be nice to make that as default? I don't see any disadvantage of not using bun |
It won't be as easy as just stating "let's make a different interpreter the default".
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. |
how i can make it permament and then how i can leave it as default? |
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: That would mean that if you really want to use bun by default, either modify that file manually or use typescript extension. |
I can't get pm2 to work with bun at all. Whatever I do pm2 always gives this error:
I have tried with command line arguments and with a configuration file. Still it seems to ignore the interpreter argument completely.
ecosystem.json:
|
pm2 logs uses 30% of resources of my machine, im using it on a potato but a bun version would be great
The text was updated successfully, but these errors were encountered: