Open dhamaniasad opened 7 years ago
I have the same issue. +1
I have the exact same issue. +1
I dont have this errror anymore. I dont know exactly what i did to fix, but it was likely making sure the version of node and npm installed on the target match the version used in Meteor. I use nvm and run the following on the target machine.
nvm install `meteor node -v`
npm install --global npm@`meteor npm -v`
I didn't figure out how to do this in a post-deploy script or how to force pm2 to use the correct version of node. I ended up building those commands into a cloud-init script I use to setup my target.
As far as trying to use pm2-meteor config to set the node version, try removing the ~
in the path to the nvm script and use an absolute path instead.
The version of the node should be same on client and server. For example, you can check your meteor node version "meteor node -v". (My version is currently 4.8.4). So the version of the node on the server should be 4.8.4.(This is my example)
same
I found the following situation will cause an error
meteor npm install
to install packageI created a new project, it's work.
Hi. I'm trying to use pm2-meteor to deploy an app. My settings file: https://gist.github.com/dhamaniasad/278a173c4118a093cb01a4ed5b411a24
However, pm2-meteor status reports the Node.js version as
7.7.3
, ignoring the nvm settings. And the app fails to start:Any idea what could be causing this?