Running NPM start gives autoToHTML export error from MOTD-parser

[SnelleJaapie]

I am kinda clueless at this point as to what to do. Maybe it simply has to do with the fact that I am running this on a Raspberry PI 5 with RBP OS?
I installed everything according to the documentation on a Paper server, by manually downloading the ZIP and extracting it in my server folder and changing some config options (just motd title and version). Also running the latest version of paper 1.20.4 (which is supperted according to the node protecol), but even 1.20.2 doesn't work.

When I run npm start, it will start up untill [> tsc] log.. it pauses for a bit and then throws the following error:
`

[email protected] prebuild
rimraf ./build/ ./bin/ && cpx-fixed "views/**/." build/views

[email protected] build
run-s build:typescript build:bin

[email protected] build:typescript
tsc

src/sleepingHelper.ts:4:10 - error TS2724: '"@sfirew/minecraft-motd-parser"' has no exported member named 'autoToHtml'. Did you mean 'autoToHTML'?

4 import { autoToHtml, cleanTags } from "@sfirew/minecraft-motd-parser";

Found 1 error in src/sleepingHelper.ts:4
`

However, when I go into the build folder that is generated, and I run sleepingserverstarter.js using node, it runs, when I refresh the server list I also get the log "a prince has taken a quick peek", but when I try to connect it doesn't work...

Is this a bug atm or is this particularly on my part?

[darkwolf682]

same problem

[SnelleJaapie]

Main problem not fixed yet, but this worked for me, for linux/RBP users (loginMessage shows error, but server starts)

It's presented in the documentation of vincss aswell as first choice, but using the binaries seemed to work for me from this link

I used the linux-arm64 version for RaspberryPi/paper server (as per documentation).
I tried this method before but I couldn't get it to work, because I am a idiot for not reading. First time I used the linux-x64 version, which would not boot and show nothing (maybe it should've?), so arm64 did the trick.

NOTE: When using the correct Binary, I first removed all traces of the manual install through zip, that includes deleting all the files and folders that came with it. After that, starting the arm64 either through dubble click or via terminal (@pi: ./[arm64-filename]) seemed to do the trick, as to I could use a screen session and keep the thing running when closing out of windows. The binary will create a settings file for you after first launch to change stuff there.

Hope this might help some with same issue (@darkwolf682 )