WCF 2.1: NodePush startet nicht mehr nach npm update

Hi,

ich habe gerade versucht via npm update zu updaten und daraufhin wirft er einen Fehler:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using npm@1.4.21
3 info using node@v0.10.29
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart be.bastelstu.wcf.nodePush@1.0.0
6 info start be.bastelstu.wcf.nodePush@1.0.0
7 verbose unsafe-perm in lifecycle true
8 info be.bastelstu.wcf.nodePush@1.0.0 Failed to exec start script
9 error be.bastelstu.wcf.nodePush@1.0.0 start: `coffee app.coffee`
9 error Exit status 1
10 error Failed at the be.bastelstu.wcf.nodePush@1.0.0 start script.
10 error This is most likely a problem with the be.bastelstu.wcf.nodePush package,
10 error not with npm itself.
10 error Tell the author that this fails on your system:
10 error     coffee app.coffee
10 error You can get their info via:
10 error     npm owner ls be.bastelstu.wcf.nodePush
10 error There is likely additional logging output above.
11 error System Linux 3.16.0-4-amd64
12 error command "/usr/bin/nodejs" "/usr/bin/npm" "start"
13 error cwd /Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush
14 error node -v v0.10.29
15 error npm -v 1.4.21
16 error code ELIFECYCLE
17 verbose exit [ 1, true ]

Gruß,

Afox

habe ich etwas falsch gemacht oder kann das bestätigt werden?

hi, Ergebnis (wenn ich es richtig gemacht habe):

Quote

TypeError: undefined is not a function
at Object.<anonymous> (/Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/app.coffee:26:15)
at Object.<anonymous> (/Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/app.coffee:1:1)
at Module._compile (module.js:456:26)

wenn ich npm update eingebe wiederholt er immer das Gleiche:

Quote

npm update
path-to-regexp@0.1.7 node_modules/express/node_modules/path-to-regexp
chroot@0.1.7 node_modules/chroot
array-flatten@1.1.1 node_modules/express/node_modules/array-flatten
debug@0.8.1 node_modules/debug
npm WARN unmet dependency /Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/node_modules/express/node_modules/send/node_modules/http-errors requires depd@'1.1.1' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/node_modules/express/node_modules/send/node_modules/http-errors requires statuses@'>= 1.3.1 < 2' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
mime@1.3.4 node_modules/express/node_modules/send/node_modules/mime
debug@2.6.8 node_modules/express/node_modules/send/node_modules/debug
qs@6.5.0 node_modules/express/node_modules/qs
proxy-addr@1.1.5 node_modules/express/node_modules/proxy-addr
├── forwarded@0.1.0
└── ipaddr.js@1.4.0

> typechecker@2.0.8 preinstall /Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/node_modules/caterpillar/node_modules/extendr/node_modules/typechecker
> node ./cyclic.js

debug@2.6.8 node_modules/express/node_modules/debug
└── ms@2.0.0
caterpillar@2.0.9 node_modules/caterpillar
├── extendr@2.1.0 (typechecker@2.0.8)
└── readable-stream@1.1.14 (inherits@2.0.3, string_decoder@0.10.31, core-util-is@1.0.2, isarray@0.0.1)
npm WARN unmet dependency /Pfad/zum/Forum/wcf/acp/be.bastelstu.wcf.nodePush/node_modules/express/node_modules/finalhandler requires debug@'2.6.8' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
debug@2.6.8 node_modules/express/node_modules/finalhandler/node_modules/debug
└── ms@2.0.0
socket.io@1.7.4 node_modules/socket.io
├── object-assign@4.1.0
├── socket.io-adapter@0.5.0
├── has-binary@0.1.7 (isarray@0.0.1)
├── debug@2.3.3 (ms@0.7.2)
├── socket.io-parser@2.3.1 (component-emitter@1.1.2, isarray@0.0.1, json3@3.3.2, debug@2.2.0)
├── engine.io@1.8.4 (base64id@1.0.0, cookie@0.3.1, engine.io-parser@1.3.2, ws@1.1.4, accepts@1.3.3)
└── socket.io-client@1.7.4 (to-array@0.1.4, indexof@0.0.1, component-emitter@1.2.1, component-bind@1.0.0, backo2@1.0.2, object-component@0.0.3, parseuri@0.0.5, engine.io-client@1.8.4)

Display More

kannst du das denn als Fehler bestätigen also auch irgendwo reproduzieren oder ist das ein Problem, welches nur bei mir besteht?

ehm, ok aber das ist doch ein Sicherheitsding? Was soll ich jetzt machen? Es sollte doch wenigstens möglich sein bis zur letzten unterstützten Version fehlerfrei upzudaten?