tobias_r - okay, maybe this is a bit of a stupi...
okay, maybe this is a bit of a stupid issue because it's late, i'm tired, and can't find the right incantations anywhere:
how the heck do I get my SK server running again without throwing tons of errors?
setup: RP4B running bullseye, untouched for the past few months due to absence from boat and no IP connectivity.
upgraded nodejs from 18.x to 22.15 with the "curl https://deb.nodesource.com/setup_22.x | bash" method.
noticed a bunch of plugins throwing errors, remembered "oh, i think i have to run
updated npm to latest, then tried rebuild. failed due to some error while compiling $stuff.
did the
it's always the same package that craps out: better-sqlite3@7.6.2 - no idea where that dependency is coming from.
deleted (well, tgz'd and then deleted) the node_modules directory in /home/pi/.signalk, tried pulling everything again with
googling the error messages just turned up one thread on the node-gyp github repo where the recommendation was to "remove the dependency, and maybe downgrade to the latest LTS version".. huh?
anybody got any hints on what to try next?
how the heck do I get my SK server running again without throwing tons of errors?
setup: RP4B running bullseye, untouched for the past few months due to absence from boat and no IP connectivity.
upgraded nodejs from 18.x to 22.15 with the "curl https://deb.nodesource.com/setup_22.x | bash" method.
noticed a bunch of plugins throwing errors, remembered "oh, i think i have to run
npm rebuildupdated npm to latest, then tried rebuild. failed due to some error while compiling $stuff.
did the
apt upgrade && apt updateit's always the same package that craps out: better-sqlite3@7.6.2 - no idea where that dependency is coming from.
deleted (well, tgz'd and then deleted) the node_modules directory in /home/pi/.signalk, tried pulling everything again with
npm installgoogling the error messages just turned up one thread on the node-gyp github repo where the recommendation was to "remove the dependency, and maybe downgrade to the latest LTS version".. huh?
anybody got any hints on what to try next?
