Sorry to hear you’re having problems. It looks like npm reports errors even when it succeeds with the install. Can you try redirecting the output of the npm install command by adding 2>&1 to the end of the command and see if that helps.
While that would work and getting rid of the error flagging, how can I tell what is actually causing it to error itself? I don’t see anywhere in the logs where it is producing anything that looks like an error.
NPM reports some information on the sterr console, instead of the stout console. It looks like the downloading of the precompiled libxmljs library from https://github.com/libxmljs/libxmljs/releases is reported as an error even when it isn’t.
Because these messages are reported on stderr Octopus Deploy sees them and thinks the process has failed. However the exit code of the process is 0, which is what Octopus Deploy cares about most. So you’re seeing fail messages in the log, but the process is still deploying successfully.