You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pm2 shows an error and cannot be executed.
I was able to run it in the previous version.
How can we reproduce it ?
run "pm2 start ecosystem.config.js --env production"
Relevant log output
0|Pulsar | WARNING: NODE_ENV value of 'production' did not match any deployment config file names.
0|Pulsar | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|Pulsar | WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
0|Pulsar | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|Pulsar | { Error: Cannot find module 'node:crypto'
0|Pulsar | at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
0|Pulsar | at Module.Hook._require.Module.require (/usr/local/lib/node_modules/pm2/node_modules/require-in-the-middle/index.js:61:29)
Code of Conduct
I agree to follow Pulsar's Code of Conduct
The text was updated successfully, but these errors were encountered:
This seems to be an issue linked to the latest security improvement, the module node:crypto was first introduced in node 15.x . Can you try upgrading to node 16.10.0 ? If this still fails, then I'll need the full log to understand what is actually happening.
Contact Details
yuan@white-paper.jp
What happened ?
pm2 shows an error and cannot be executed.
I was able to run it in the previous version.
How can we reproduce it ?
run "pm2 start ecosystem.config.js --env production"
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: