Skip to content
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

Nodemon is not working when it run with forever. #71

Closed
coconutperm opened this issue Feb 9, 2017 · 5 comments
Closed

Nodemon is not working when it run with forever. #71

coconutperm opened this issue Feb 9, 2017 · 5 comments
Assignees

Comments

@coconutperm
Copy link
Collaborator

coconutperm commented Feb 9, 2017

forever's child process cannot find nodemon package.
I guess this problem is spawn's path issue by --prefix option of npm.

======================================

  • Error logs.
    events.js:160
    throw er; // Unhandled 'error' event
    ^

Error: spawn nodemon ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

@coconutperm coconutperm changed the title Nodemon is not working if it run with forever. Nodemon is not working when it run with forever. Feb 9, 2017
@coconutperm coconutperm self-assigned this Feb 9, 2017
@coconutperm
Copy link
Collaborator Author

coconutperm commented Feb 9, 2017

* Identified : Child process cannot use path of script, can use global path only.

=> This is solved. we need add 'export' to path of run script.

@coconutperm
Copy link
Collaborator Author

  • Identified : Child process use only pull file name like 'nodemon.cmd'.

So I report to 'forever' module repo. and i will find workaround for our project.
foreversd/forever-monitor#140

@coconutperm
Copy link
Collaborator Author

I found new solution.

http://pm2.keymetrics.io/

romandev added a commit that referenced this issue Feb 23, 2017
This CL includes the follwing things.
 - Improve existing scripts.
 - Introduce |absolute| command for all platforms.
 - After this patch, we can add a new subcommand easily in bootstrap/command/.
 - Introduce very simple platform test. The test will be more improved later.
 - Fix a bug that executable files are located in server/ on windows (#69).
 - Remove unnecesary script parts in package.json
 - Stop to use nodemon until fixing it (#71)
romandev added a commit that referenced this issue Feb 23, 2017
This CL includes the follwing things.
 - Improve existing scripts.
 - Introduce |absolute| command for all platforms.
 - After this patch, we can add a new subcommand easily in bootstrap/command/.
 - Introduce very simple platform test. The test will be more improved later.
 - Fix a bug that executable files are located in server/ on windows (#69).
 - Remove unnecesary script parts in package.json
 - Stop to use nodemon until fixing it (#71)
romandev added a commit that referenced this issue Feb 23, 2017
This CL includes the follwing things.
 - Improve existing scripts.
 - Introduce |absolute| command for all platforms.
 - After this patch, we can add a new subcommand easily in bootstrap/command/.
 - Introduce very simple platform test. The test will be more improved later.
 - Fix a bug that executable files are located in server/ on windows (#69).
 - Remove unnecesary script parts in package.json
 - Stop to use nodemon until fixing it (#71)
@toficofi
Copy link

toficofi commented Mar 8, 2017

This is caused by nodejs/node-v0.x-archive#2318
As a workaround, add spawnWith: {shell: true} to your config.

romandev added a commit that referenced this issue Sep 30, 2017
This CL includes the follwing things.
 - Improve existing scripts.
 - Introduce |absolute| command for all platforms.
 - After this patch, we can add a new subcommand easily in bootstrap/command/.
 - Introduce very simple platform test. The test will be more improved later.
 - Fix a bug that executable files are located in server/ on windows (#69).
 - Remove unnecesary script parts in package.json
 - Stop to use nodemon until fixing it (#71)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants