I would like to try out your fork, but I have no experience installing via npm. I think all I need is a small nudge. I appreciate your time.
33047 info lifecycle express@4.16.2~postinstall: express@4.16.2
33048 silly lifecycle express@4.16.2~postinstall: no script for postinstall, continuing
33049 silly postinstall jquery@3.2.1 /root/node_modules/.staging/jquery-b59a09bb
33050 info lifecycle jquery@3.2.1~postinstall: jquery@3.2.1
33051 silly lifecycle jquery@3.2.1~postinstall: no script for postinstall, continuing
33052 silly postinstall jsdom@9.12.0 /root/node_modules/.staging/jsdom-2a37b832
33053 info lifecycle jsdom@9.12.0~postinstall: jsdom@9.12.0
33054 silly lifecycle jsdom@9.12.0~postinstall: no script for postinstall, continuing
33055 silly postinstall less@2.7.2 /root/node_modules/.staging/less-f0e1e33d
33056 info lifecycle less@2.7.2~postinstall: less@2.7.2
33057 silly lifecycle less@2.7.2~postinstall: no script for postinstall, continuing
33058 silly postinstall mocha@3.5.3 /root/node_modules/.staging/mocha-f412a990
33059 info lifecycle mocha@3.5.3~postinstall: mocha@3.5.3
33060 silly lifecycle mocha@3.5.3~postinstall: no script for postinstall, continuing
33061 silly postinstall sinon@1.17.7 /root/node_modules/.staging/sinon-2e3919d5
33062 info lifecycle sinon@1.17.7~postinstall: sinon@1.17.7
33063 silly lifecycle sinon@1.17.7~postinstall: no script for postinstall, continuing
33064 silly postinstall sinon-chai@2.14.0 /root/node_modules/.staging/sinon-chai-8c6d0458
33065 info lifecycle sinon-chai@2.14.0~postinstall: sinon-chai@2.14.0
33066 silly lifecycle sinon-chai@2.14.0~postinstall: no script for postinstall, continuing
33067 silly postinstall socket.io@1.7.4 /root/node_modules/.staging/socket.io-cd20b973
33068 info lifecycle socket.io@1.7.4~postinstall: socket.io@1.7.4
33069 silly lifecycle socket.io@1.7.4~postinstall: no script for postinstall, continuing
33070 silly postinstall winston@2.4.0 /root/node_modules/.staging/winston-469566aa
33071 info lifecycle winston@2.4.0~postinstall: winston@2.4.0
33072 silly lifecycle winston@2.4.0~postinstall: no script for postinstall, continuing
33073 silly postinstall log.io@0.3.6 /root/node_modules/.staging/log.io-3ed1c850
33074 info lifecycle log.io@0.3.6~postinstall: log.io@0.3.6
33075 verbose lifecycle log.io@0.3.6~postinstall: unsafe-perm in lifecycle false
33076 verbose lifecycle log.io@0.3.6~postinstall: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/root/node_modules/log.io/node_modules/.bin:/root/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
33077 verbose lifecycle log.io@0.3.6~postinstall: CWD: /root/node_modules/log.io
33078 silly lifecycle log.io@0.3.6~postinstall: Args: [ '-c', 'cake build && cake ensure:configuration' ]
33079 silly lifecycle log.io@0.3.6~postinstall: Returned: code: 1 signal: null
33080 info lifecycle log.io@0.3.6~postinstall: Failed to exec postinstall script
33081 verbose unlock done using /root/.npm/_locks/staging-4b9e621e77c1ced6.lock for /root/node_modules/.staging
33082 silly rollbackFailedOptional Starting
33083 silly rollbackFailedOptional Finishing
33084 silly runTopLevelLifecycles Finishing
33085 silly install printInstalled
33086 warn enoent ENOENT: no such file or directory, open '/root/package.json'
33087 verbose enoent ENOENT: no such file or directory, open '/root/package.json'
33087 verbose enoent This is most likely not a problem with npm itself
33087 verbose enoent and is related to npm not being able to find a file.
33088 warn root No description
33089 verbose If you need help, you may report this error at:
33089 verbose <https://github.com/npm/npm/issues>
33090 warn root No repository field.
33091 verbose If you need help, you may report this error at:
33091 verbose <https://github.com/npm/npm/issues>
33092 warn root No README data
33093 verbose If you need help, you may report this error at:
33093 verbose <https://github.com/npm/npm/issues>
33094 warn root No license field.
33095 verbose If you need help, you may report this error at:
33095 verbose <https://github.com/npm/npm/issues>
33096 verbose stack Error: log.io@0.3.6 postinstall: `cake build && cake ensure:configuration`
33096 verbose stack Exit status 1
33096 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
33096 verbose stack at emitTwo (events.js:106:13)
33096 verbose stack at EventEmitter.emit (events.js:191:7)
33096 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
33096 verbose stack at emitTwo (events.js:106:13)
33096 verbose stack at ChildProcess.emit (events.js:191:7)
33096 verbose stack at maybeClose (internal/child_process.js:920:16)
33096 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
33097 verbose pkgid log.io@0.3.6
33098 verbose cwd /root
33099 error Linux 3.10.0-693.2.2.el7.x86_64
33100 error argv "/usr/bin/node" "/usr/bin/npm" "install" "https://github.com/HansHammel/Log.io.coffee" "--user" "root"
33101 error node v6.11.3
33102 error npm v3.10.10
33103 error code ELIFECYCLE
33104 error log.io@0.3.6 postinstall: `cake build && cake ensure:configuration`
33104 error Exit status 1
33105 error Failed at the log.io@0.3.6 postinstall script 'cake build && cake ensure:configuration'.
33105 error Make sure you have the latest version of node.js and npm installed.
33105 error If you do, this is most likely a problem with the log.io package,
33105 error not with npm itself.
33105 error Tell the author that this fails on your system:
33105 error cake build && cake ensure:configuration
33105 error You can get information on how to open an issue for this project with:
33105 error npm bugs log.io
33105 error Or if that isn't available, you can get their info via:
33105 error npm owner ls log.io
33105 error There is likely additional logging output above.
I would like to try out your fork, but I have no experience installing via npm. I think all I need is a small nudge. I appreciate your time.