meanjs 0.4.0 funktioniert nicht bei der Bereitstellung auf Heroku

Question

Ich habe gerade versucht die Meanjs 0.4.0 in lokalen Host und läuft gut, aber wenn ich Heroku link to app bereitstellen und versuchen Sie die "Registrieren" -Option bekomme ich das im Navegator Konsole:

POST https://meanjsapptest.herokuapp.com/api/auth/signup 503 (Service Unavailable) 

und wenn ich die comand Heroku Protokolle in der CLI schreiben erhalte ich:

2017-06-06T04:15:35.152983+00:00 app[web.1]: (node:16) DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html 
2017-06-06T04:15:35.153005+00:00 app[web.1]: crypto.js:635 
2017-06-06T04:15:35.153006+00:00 app[web.1]: throw new TypeError(
2017-06-06T04:15:35.153006+00:00 app[web.1]:^
2017-06-06T04:15:35.153007+00:00 app[web.1]: 
2017-06-06T04:15:35.153008+00:00 app[web.1]: TypeError: The "digest" argument is required and must not be undefined 
2017-06-06T04:15:35.153009+00:00 app[web.1]: at pbkdf2 (crypto.js:635:11) 
2017-06-06T04:15:35.153010+00:00 app[web.1]: at Object.exports.pbkdf2Sync (crypto.js:628:10) 
2017-06-06T04:15:35.153012+00:00 app[web.1]: at model. (/app/modules/users/server/models/user.server.model.js:112:26) 
2017-06-06T04:15:35.153011+00:00 app[web.1]: at model.UserSchema.methods.hashPassword (/app/modules/users/server/models/user.server.model.js:123:19) 
2017-06-06T04:15:35.153013+00:00 app[web.1]: at _next (/app/node_modules/hooks-fixed/hooks.js:62:30) 
2017-06-06T04:15:35.153013+00:00 app[web.1]: at fnWrapper (/app/node_modules/hooks-fixed/hooks.js:186:8) 
2017-06-06T04:15:35.153014+00:00 app[web.1]: at model. (/app/node_modules/mongoose/lib/plugins/saveSubdocs.js:20:7) 
2017-06-06T04:15:35.153014+00:00 app[web.1]: at _next (/app/node_modules/hooks-fixed/hooks.js:62:30) 
2017-06-06T04:15:35.153015+00:00 app[web.1]: at fnWrapper (/app/node_modules/hooks-fixed/hooks.js:186:8) 
2017-06-06T04:15:35.153015+00:00 app[web.1]: at /app/node_modules/mongoose/lib/plugins/validateBeforeSave.js:33:13 
2017-06-06T04:15:35.153016+00:00 app[web.1]: at /app/node_modules/kareem/index.js:131:16 
2017-06-06T04:15:35.153016+00:00 app[web.1]: at _combinedTickCallback (internal/process/next_tick.js:95:7) 
2017-06-06T04:15:35.153017+00:00 app[web.1]: at process._tickCallback (internal/process/next_tick.js:161:9) 
2017-06-06T04:15:35.167579+00:00 app[web.1]: error: Forever detected script exited with code: 1 
2017-06-06T04:15:35.173500+00:00 app[web.1]: error: Script restart attempt #1 
2017-06-06T04:15:35.292903+00:00 app[web.1]: 
2017-06-06T04:15:35.294191+00:00 app[web.1]: 
2017-06-06T04:15:35.310954+00:00 app[web.1]: + Error: Certificate file or key file is missing, falling back to non-SSL mode 
2017-06-06T04:15:35.311037+00:00 app[web.1]: To create them, simply run the following from your shell: sh ./scripts/generate-ssl-certs.sh 
2017-06-06T04:15:35.311039+00:00 app[web.1]: 
2017-06-06T04:15:35.916892+00:00 app[web.1]: Db.prototype.authenticate method will no longer be available in the next major release 3.x as MongoDB 3.6 will only allow auth against users in the admin db and will no longer allow multiple credentials on a socket. Please authenticate using MongoClient.connect with auth credentials. 

ich weiß nicht, was jetzt zu tun, weil Heroku mir der Fehler thar unterstützt sagen ist in meinem Code, aber ich habe dort nichts geändert!

CLI screenshot

Answer 1

Gerade hatte dieses Problem. Wir konnten es beheben, indem wir unsere bevorzugte Knotenversion in package.json> engines durchsetzten.

Wir hatten es zuvor bei

"node": ">=0.10.0" 

Wir es

"node": "6.6.0" 

zu

geändert und schob dann das zu Heroku, und dass das Problem behoben.

Nicht ganz sicher, was das Problem ist, aber wir fanden diesen Link, die uns führen die Knoten-Version zu glauben, das Problem war:

https://github.com/nodejs/node/wiki/Breaking-changes-between-v4-LTS-and-v6-LTS#crypto