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

Problems with easyNOMP - Nodejs version, NPM version or PM2 #188

Open
Cadence-The-Developer opened this issue Nov 12, 2021 · 0 comments
Open

Comments

@Cadence-The-Developer
Copy link

Hey guys,

which versions of nodejs, npm, pm2 and ubuntu are you using to run easyNOMP? Whatever I do, either NPM or PM2 are not

Currently installed versions

  • Ubuntu 20
  • NVM 0.39.0
  • Nodejs 8.1.4
  • NPM 5.0.3

When I wanted to launch PM2 in any way I received

/usr/local/lib/node_modules/pm2/node_modules/chalk/source/index.js:103
...styles,
^^^

SyntaxError: Unexpected token ...
at createScript (vm.js:74:10)
at Object.runInThisContext (vm.js:116:10)
at Module._compile (module.js:533:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (/usr/local/lib/node_modules/pm2/constants.js:10:14)

Before when PM2 was working (I think i used NodeJS 8.1.17). NPM was not.

I was received errors like

Error: The module '/yyyyyyy/xxxxxxx/EasyNOMP/node_modules/bignum/binding/bignum.node'
0|pool | was compiled against a different Node.js version using
0|pool | NODE_MODULE_VERSION 57. This version of Node.js requires
0|pool | NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
0|pool | the module (for instance, using npm rebuild or npm install).

(node:1569) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): SyntaxError: Unexpected token ...
(node:1569) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

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

1 participant