So, I’ve installed MineOS on Ubuntu-Server 18.04 LTS once. But now I’m on Debian 10 and I can’t get it to start. First I tried mineos-node, and of course, it didn’t work. Awhile after I tried the systemd version. And yeah it didn’t work.
I’m sorry if my English is bad, it’s not my primary language
This is the problem. This is a module that should have been installed already through the use of the npm install command. It probably failed; I’m guessing you’re using NodeJS version > 8.x?
Try this, as root
npm install fs-extra
If you get errors, those are the specific errors we want to see. It probably will tell us that this module, which is definitely necessary, isn’t compatible with … Node10 or Node12…or something to that effect. Which tells us also that your NodeJS version needs to be downgraded (removed and specifically installing Node8)
The steps in all the wikipages should definitely have installed Node8, so that’s another thing I’m interested in finding out–why any other version may have made it onto your system instead.
Node 8 and Node 10 are pretty different, and dependencies aren’t expected to work from between those versions. Basically, it was like Node1 -> Node 8 which shared a common API. After Node 8, they took the years of things they learned and made a new one…think Python 2 -> Python 3. Similar in so many ways, but not enough to be inter compatible.
So you potentially then, skipped this step, which adds Node8 repositories to Apt.
If you didn’t do that step, apt will default to Debian 10 default repos which contain apparently v10.15.2.
Default debian 10 repos keep npm separate, so that explains command not found.
So to remedy this:
Using apt, remove node10.
Using the commands in the wiki linked above, put the Node8 repos in as a download candidate.
Using apt again, install Node8. The installed packages should clearly indicate the version is 8.
Having used the Node8 repos, npm will be included automatically, and the npm install command would work.
You can try installing node10 with npm, but if it doesn’t work, it’s likely you’ll see errors where dependencies don’t build properly–and the reason is likely the same as the one this user experienced.
It looks like the nodesource folks fail to take into account the possibility of Debian/Ubuntu already having a newer version than the one they want you to install. This will affect any distribution released in the last year or so. This issue has been reportedmultipletimes yet no one seems to be in a rush to fix this bug. One workaround is to use package pinning such that the older node8 gets preferred over the newer node10, either by boosting the nodesource packages, or deprioritising the debian packages.