Other Node swc/core issues (core-freebsd-x64, keepImportAttributes, keepImportAssertions)

Espionage724

Espionage724

I tried doing npm start and got a Bindings not found error. I did npm install @swc/core-freebsd-x64 and got the keepImportAttributes vs keepImportAssertions error.

Trying to run it through linux got ENOSYS: function not implemented, watch.

I thought downgrading swc/core to 1.3.82 to before the name switch could work, but it seems 2004Scape switched to needing node-register as a requirement over ts and register (apparently) needs a higher swc/core version. I don't know enough about the code to try to fix it directly.

I'm thinking the devs could do something BSD-specific for the Attributes vs Assertions error, but I'm thinking there's also something odd about the node module versions in-general (I heard core-freebsd-x64 only supports FreeBSD 13)?

The bindings error seems like FreeBSD isn't in a list to be auto-downloaded since manually-installing it solves the binding error? Maybe I need a specific core-freebsd-x64 version? I've ran the same project on Fedora 40, openSUSE TW, and Windows 10 no problem from git clone, to npm start, and then it running.

Does anyone have any ideas?
 
Still looking to get 2004Scape running on FreeBSD! I really want to play some RuneScape :p
  • Running natively (node/npm/openjdk from pkg) got ImportAttributes vs ImportAssertions
  • Running through Wine got issues related to bcrypt
  • Running through Linux layer (c7 or rl9) got ENOSYS errors with FSWatcher

I'm thinking one sure-fire method would be VirtualBox, Linux, and then 2004Scape server running within that, but that's a lot of stuff for a small server.
 
Anyone have any ideas on this? I like FreeBSD but this is a show-stopper currently (I need RuneScape :p)

I have up-to-date 2004Scape-Server Linux notes here. This is basically all that's needed to get it up and running to the issue on FreeBSD 14.1:

Code: 
pkg install git-lite node22 openjdk22 npm-node22

Code: 
cd ~ && mkdir -p ~/'Projects' && rm -Rf ~/'Projects/2004Scape-Server/src' && git clone --branch 'main' --depth '1' --recurse-submodules 'https://github.com/2004Scape/Server.git' ~/'Projects/2004Scape-Server/src' && sync

Code: 
cd ~/'Projects/2004Scape-Server/src' && npm start

Edit: I got it working from a 64-bit Wine prefix on Linux (notes), but I didn't try that on FreeBSD because of something about pkg32 at the time and tried to fuss with a 32-bit prefix instead (bcrypt doesn't build without huge VS/Python/etc deps; no win32 prebuilts); I'll be back with results on 14.1!

Edit: No-go; I forget the exact issue but it didn't work from 64-bit Wine (non-devel) nor wine-proton.
 
Last edited:
Espionage724 said:
Edit: No-go; I forget the exact issue but it didn't work from 64-bit Wine (non-devel) nor wine-proton.
Click to expand...

The devs created a no-dev-watcher branch for testing and I got it up and running through a 64-bit Win10 Wine prefix! (notes)

Not exactly a fix for the native FreeBSD-specific swc bindings issue though (still got wasm error at first + InvalidArg after installing freebsd-x64 core; very likely not a proper troubleshooting step for this), but for this particular situation I can tolerate running the stuff through Wine fine!
 
You must log in or register to reply here.
Back
Top