That seems more likely that the file didn’t have the +x
attribute to make it executable.
["Error: Cannot find module '/usr/games/minecraft/node_modules/userid/build/Debug/userid.node'","
This suggests that there were errors compiling npm install userid
(implied via npm install --unsafe-perms
).
In fact, I notice userid
shows up in that error log 1500 times. I think that’s a pretty clear indicator that we should look at that module specifically, and verify it really does build.
And doing that often means removing previous attempts, e.g., deleting /usr/games/minecraft/node_modules
.
It’s uncertain, for example, whether it’s actually rebuilding userid
or if it’s identifying that “hey it’s already there, so let’s use whats already there.” Maybe it is doing exactly what we want, then we just have to find out why userid
is problematic on your installation, unlike anywhere I’ve ever seen.
In the hundreds of lines of output, I see this only once:
> userid@0.3.1 install /usr/games/minecraft/node_modules/userid
> node-gyp rebuild
make: Entering directory '/usr/games/minecraft/node_modules/userid/build'
CXX(target) Release/obj.target/userid/src/userid.o
SOLINK_MODULE(target) Release/obj.target/userid.node
COPY Release/userid.node
make: Leaving directory '/usr/games/minecraft/node_modules/userid/build'
So I guess we can try these steps, but–again, let’s not do this with sudo
, let’s do it as root
, as the instructions advise. sudo
and root
are wholly different, and that difference usually is rather benign, but since we’re seeing an error I’ve literally never seen before, it’s worth taking the extra care to point out any irregularity or process.
cd /usr/games/minecraft/
rm -rf node_modules
npm install --unsafe-perms