We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It bombs right here:
goof-mongo | {"t":{"$date":"2022-11-30T01:11:58.349+00:00"},"s":"I", "c":"NETWORK", "id":23016, "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}} goof | goof | > [email protected] start /usr/src/goof goof | > NODE_OPTIONS=--openssl-legacy-provider node app.js goof | goof | node: --openssl-legacy-provider is not allowed in NODE_OPTIONS goof | npm ERR! code ELIFECYCLE goof | npm ERR! errno 9 goof | npm ERR! [email protected] start: `NODE_OPTIONS=--openssl-legacy-provider node app.js` goof | npm ERR! Exit status 9 goof | npm ERR! goof | npm ERR! Failed at the [email protected] start script. goof | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. goof | goof | npm ERR! A complete log of this run can be found in: goof | npm ERR! /root/.npm/_logs/2022-11-30T01_11_58_558Z-debug.log goof exited with code 9
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It bombs right here:
The text was updated successfully, but these errors were encountered: