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
PM2 doesnt with with Bun #4949
Comments
Related? #4327 |
Can confirm, am experiencing the same issue. |
I run bun with pm2 successfully with this setup:
|
@vuongphamaioz, I did to, but got this error " errored " if we set |
@calebeaires I just tried |
@vuongphamaioz It were in Nuxt 3 |
Thanks for reporting this issue, there are 2 issues here: |
I used this: |
Any update on this issue ? |
The only thing we are not using Bun in production is that we would like to take advantage of multi-core. The link to cluster module issue: |
any way to serve using bun pm2 serve -s build 3000 --spa like this? |
@sancho1952007 try this
|
Thanks, I'll try it later! |
bun i -g pm2 By the way, is "bun pm2 start app.js" "node app.js"? Or is it "bun app.js"? |
Both of the issues have been fixed:
If you're still experiencing issues with |
For me it looks like pm2 does not support bun anymore and ignores the interpreter flag completely:
|
Same issue here |
The The problem you're facing (and myself; because I ended up here :) ) is that the pm2 script relies on $: cat $(which pm2)
#!/usr/bin/env node
require('../lib/binaries/CLI.js');
$: Usually To work around this I have installed |
Any update on this issue? Pm2 -i 3 --interpreter=bun runs instances in FORK mode instead of Cluster mode. Bun version: 1.1.6 |
What version of Bun is running?
1.0.0+822a00c4d508b54f650933a73ca5f4a3af9a7983
What platform is your computer?
Linux 5.15.49-linuxkit aarch64 unknown
What steps can reproduce the bug?
Create Dockerfile:
You get:
/bin/sh: 1: pm2: not found
So you try:
What is the expected behavior?
Show version. Ultimate goal is to later do
pm2 start --no-daemon 'bun src/server.ts'
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: