-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Error "Script not found" when running pm2 start npm -- start
#4811
Comments
pm2 start npm -- start
I more or less get the same error whenever I try to give a name to my app... for exemple:
|
Well.... solved it by adding a trailing \ after app.js so:
|
@dlinning-jockey ,did you fixed it already? |
@heavenkiller2018 I have not. This is still a standing bug. |
Still not working. |
This is still an issue. There is a workaround for it by giving npm file path in the script . #3657 We are already using pm2 in production. We are trying to change local development to Docker and its not working due to this script issue. I think this is supposed to be a feature which was implemented in #1317 but its failing now. Can pm2 team take a look please. |
Hello, Hope it helps! |
I cant run app in production mode with this solution :) |
it works for me , thanks ! ! but there is still a question , I run 'pm2 start deploy.json', it runs the dev version.
|
You can add start as args in deploy.json file : "script": "./node_modules/next/dist/bin/next", |
I don't think it is working. scripts: { deploy.json } pm2 start deploy.json |
It worked, thank you so much |
Pra mim resolveu aplicando o comando abaixo. Fazendo a instalação do ts-node |
still this issue is active |
Had same issue |
This has been an issue since 2020 and it's still not fixed!? |
any solution ? |
thank you so much it's working for me |
What's going wrong?
When trying to run a Next.js based site via PM2 through an npm script, the error above is thrown. See output below:
How could we reproduce this issue?
package.json
Command:
pm2 start npm --name "app" -- start
Supporting information
OS: Windows 10
NPM Path:
report.txt
The text was updated successfully, but these errors were encountered: