jdx / npm-register

Your own private npm registry and backup server
ISC License
483 stars 68 forks source link

Heroku Button Deploy not working #106

Closed forest closed 6 years ago

forest commented 6 years ago

Here is the output when trying to start the app.

I verified the S3 access and the htpasswd file.

Any suggestions?

2018-05-03T00:28:18.914414+00:00 heroku[web.1]: State changed from crashed to starting
2018-05-03T00:28:24.034003+00:00 heroku[web.1]: Starting process with command `npm start`
2018-05-03T00:28:26.732216+00:00 app[web.1]:undefined
2018-05-03T00:28:26.732233+00:00 app[web.1]: > npm-register@2.6.4 start /app
2018-05-03T00:28:26.732235+00:00 app[web.1]: > node bin/npm-register start
2018-05-03T00:28:26.732236+00:00 app[web.1]:undefined
2018-05-03T00:28:27.162531+00:00 app[web.1]: Opbeat agent is inactive due to configuration
2018-05-03T00:28:27.594321+00:00 app[web.1]: node[20]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
2018-05-03T00:28:27.595069+00:00 app[web.1]:  1: node::Abort() [node]
2018-05-03T00:28:27.595719+00:00 app[web.1]:  2: 0x87b6c5 [node]
2018-05-03T00:28:27.596299+00:00 app[web.1]:  3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [node]
2018-05-03T00:28:27.596933+00:00 app[web.1]:  4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [node]
2018-05-03T00:28:27.597547+00:00 app[web.1]:  5: 0xad5b9f [node]
2018-05-03T00:28:27.598173+00:00 app[web.1]:  6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [node]
2018-05-03T00:28:27.598217+00:00 app[web.1]:  7: 0x12a21508427d
2018-05-03T00:28:27.606326+00:00 app[web.1]: Aborted
2018-05-03T00:28:27.611283+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-05-03T00:28:27.611866+00:00 app[web.1]: npm ERR! errno 134
2018-05-03T00:28:27.613861+00:00 app[web.1]: npm ERR! npm-register@2.6.4 start: `node bin/npm-register start`
2018-05-03T00:28:27.614107+00:00 app[web.1]: npm ERR! Exit status 134
2018-05-03T00:28:27.614433+00:00 app[web.1]: npm ERR!
2018-05-03T00:28:27.614655+00:00 app[web.1]: npm ERR! Failed at the npm-register@2.6.4 start script.
2018-05-03T00:28:27.614885+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2
jdx commented 6 years ago

it seems to not be compatible with node 10 for some reason https://github.com/jdxcode/npm-register/commit/89b30b9bb0cb39eca0ddedb766a9f23b5ce3890c