Shinobi package broken

[baslking]

With the latest update:
last-modified: Sun, 26 Oct 2025 06:27:35 GMT
1761460055

The node.js starts but web access gives:
TypeError: s.getConfigWithBranding is not a function
at /usr/share/shinobi/libs/webServerPaths.js:135:76
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/share/shinobi/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/usr/share/shinobi/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at /usr/share/shinobi/node_modules/express/lib/router/index.js:281:22
at router.process_params (/usr/share/shinobi/node_modules/express/lib/router/index.js:335:12)
at next (/usr/share/shinobi/node_modules/express/lib/router/index.js:275:10)
at /usr/share/shinobi/libs/webServerPaths.js:100:9
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/share/shinobi/node_modules/express/lib/router/index.js:317:13)
at /usr/share/shinobi/node_modules/express/lib/router/index.js:284:7
at router.process_params (/usr/share/shinobi/node_modules/express/lib/router/index.js:335:12)
at next (/usr/share/shinobi/node_modules/express/lib/router/index.js:275:10)
at urlencodedParser (/usr/share/shinobi/node_modules/body-parser/lib/types/urlencoded.js:91:7)
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)

[graysky]

TY for letting me know. Please try r3831.76c22bcb-1 when it hits the repos.

[baslking]

Not any better unfortunately

[code]TypeError: s.getConfigWithBranding is not a function
at /usr/share/shinobi/libs/webServerPaths.js:152:71
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/share/shinobi/node_modules/express/lib/router/route.js:149:13)
at Route.dispatch (/usr/share/shinobi/node_modules/express/lib/router/route.js:119:3)
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at /usr/share/shinobi/node_modules/express/lib/router/index.js:284:15
at router.process_params (/usr/share/shinobi/node_modules/express/lib/router/index.js:346:12)
at next (/usr/share/shinobi/node_modules/express/lib/router/index.js:280:10)
at cors (/usr/share/shinobi/node_modules/cors/lib/index.js:188:7)
at /usr/share/shinobi/node_modules/cors/lib/index.js:224:17
at originCallback (/usr/share/shinobi/node_modules/cors/lib/index.js:214:15)
at /usr/share/shinobi/node_modules/cors/lib/index.js:219:13
at optionsCallback (/usr/share/shinobi/node_modules/cors/lib/index.js:199:9)
at corsMiddleware (/usr/share/shinobi/node_modules/cors/lib/index.js:204:7)
at Layer.handle [as handle_request] (/usr/share/shinobi/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/share/shinobi/node_modules/express/lib/router/index.js:328:13)[/code]

[graysky]

Can you check to see if the AUR package on x86/64 also fails? If so, it is nothing we are doing in our packaging/builds. I do not use Shinobi any more so I have nothing preconfigured for testing.

[baslking]

I have an X84 that I can try an install on when I get time. I'm currently only running an Arm Arch. I expect the problem is that Node.js was upgraded to 25.0 The Shinobi site says only 16.x works, but the Node v24 that just broke has been the most stable for me for a few months. Lots of deprecated node packages but it has been working quite reliably.

[graysky]

Please report back. If the problem is with the source package which in this case is the AUR package, whatever should be corrected there so I can mirror it in our repo.

[baslking]

I've been too busy and travelling to try the AMD64 version but I just tried reverting to the Node.js version 24( nodejs-lts-krypton) and that seems to work fine. So Node 25 breaks Shinobi on Arm64 at least for now.

[graysky]

I am going to remove the package from our aur repo. Users can build from the AUR.

[baslking]

That probably makes sense, especially if you can't test it. I don't see any reason for it to be in the Arch distribution when its not in the X86 distribution. I got the same results from the AUR build as I did with the packaged one. Maybe I'm the only one using it?
Thanks for including it initally anyway its Arch packaging works well.