NPM run build issue

[Laukage]

I can't get minetrack to run on this machine for some reason..
Not sure if its because it is arm based cpu?

Stack trace when running "NPM run build"
https://mclo.gs/XQNIlbI

[hugmanrique]

According to parcel-bundler/source-map#33, the Rust rewrite of source-map should fix this issue. The fix should be included in Parcel 2.0.0-beta.3.1, but I'm not sure. Could you try pining parcel to that version in the package.json file, run npm i, and try again?

[Laukage]

According to parcel-bundler/source-map#33, the Rust rewrite of source-map should fix this issue. The fix should be included in Parcel 2.0.0-beta.3.1, but I'm not sure. Could you try pining parcel to that version in the package.json file, run npm i, and try again?

I'm not sure what any of that means xD

[hugmanrique]

My bad, replace beta.2 by beta.3.1 in this line

Minetrack/package.json

Line 48 in 41060dc

"parcel": "^2.0.0-beta.2"

, then run npm i and try building the client (as specified in the README file, i.e. as you did when filling this issue). Does the same error message appear?

[Laukage]

i replaced "Beta.2" with "Beta.3.1.
Ran "NPM I"
then i ran "npm run build"

still getting somewhat the same error:
https://mclo.gs/dxdFEdz

[Laukage]

My bad, replace beta.2 by beta.3.1 in this line

Minetrack/package.json

Line 48 in 41060dc

"parcel": "^2.0.0-beta.2"

, then run npm i and try building the client (as specified in the README file, i.e. as you did when filling this issue). Does the same error message appear?

Do you happen to know what my issue might be or have any troubleshooting steps i can take?

[hugmanrique]

There's no need to ask for etas, we will reply when available. Anyways, we need the @parcel/source-map version. Can you post the output of npm view @parcel/source-map? If it returns 2.0.0-alpha.4.18, we will post an issue on the upstream project. Otherwise, you can try explicitly adding the latest version (mentioned before) of @parcel/source-map to your package.json file and run npm i again.

[Laukage]

There's no need to ask for etas, we will reply when available. Anyways, we need the @parcel/source-map version. Can you post the output of npm view @parcel/source-map? If it returns 2.0.0-alpha.4.18, we will post an issue on the upstream project. Otherwise, you can try explicitly adding the latest version (mentioned before) of @parcel/source-map to your package.json file and run npm i again.

Sorry, i wasn't sure if you had seen it cuz it wasn't a reply - won't happen again.

I'm assuming this means i have version 2.0.0-rc.4

After manually adding "2.0.0-rc.4" to the package-lock.json it still results in the same error:

It says i need "SQLITE" module, but i already did install it through apt-get and npm install.

[hugmanrique]

Alright, now we're getting a different error, that's good! (well, not 100% good). node-sqlite3 doesn't provide precompiled binaries for linux-arm64 (see TryGhost/node-sqlite3#1413). You will need to build from source which, by reading the linked issue, seems to require python 2. Once you have python installed, try npm i again.

[Laukage]

Alright, now we're getting a different error, that's good! (well, not 100% good). node-sqlite3 doesn't provide precompiled binaries for linux-arm64 (see mapbox/node-sqlite3#1413). You will need to build from source which, by reading the linked issue, seems to require python 2. Once you have python installed, try npm i again.

That error has now gone away since i have Python2 installed, i get past "NPM I"
but now when i run "npm run build" i get this error...

[hugmanrique]

Ah, the same error is back. Will open an issue there requesting an arm64 build soon. For now, I suggest running Minetrack on x86.

[Cryptkeeper]

Until there is a sqlite3 arm build available, you will need to run on x86-64.