Why is Signalk-cloud failing to start

[seamaster101]

Hi ,
I'm running Venis OS Large Image (with signalK) on RPI 3B+
It appears that many people have the same problem as me: SignalK-cloud failed to start with an error message:
"Failed to start: Package subpath './v4' is not defined by "exports" in /data/con..."
I hope someone can help.
here is the log file if it could help
May 01 08:35:57 Could not parse security config May 01 08:35:57 ENOENT: no such file or directory, open '/data/conf/signalk/security.json' May 01 08:36:05 signalk-cloud failed to start: Package subpath './v4' is not defined by "exports" in /data/conf/signalk/node_modules/uuid/package.json May 01 08:36:05 Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v4' is not defined by "exports" in /data/conf/signalk/node_modules/uuid/package.json at throwExportsNotFound (internal/modules/esm/resolve.js:299:9) at packageExportsResolve (internal/modules/esm/resolve.js:522:3) at resolveExports (internal/modules/cjs/loader.js:449:36) at Function.Module._findPath (internal/modules/cjs/loader.js:489:31) at Function.Module._resolveFilename (internal/modules/cjs/loader.js:875:27) at Function.Module._load (internal/modules/cjs/loader.js:745:27) at Module.require (internal/modules/cjs/loader.js:961:19) at require (internal/modules/cjs/helpers.js:92:18) at Object.<anonymous> (/data/conf/signalk/node_modules/signalk-cloud/index.js:5:16) at Module._compile (internal/modules/cjs/loader.js:1072:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10) at Module.load (internal/modules/cjs/loader.js:937:32) at Function.Module._load (internal/modules/cjs/loader.js:778:12) at Module.require (internal/modules/cjs/loader.js:961:19) at require (internal/modules/cjs/helpers.js:92:18) at doRegisterPlugin (/usr/lib/node_modules/signalk-server/lib/interfaces/plugins.js:337:39) { code: 'ERR_PACKAGE_PATH_NOT_EXPORTED' } May 01 08:36:08 signalk-server running at 0.0.0.0:3000 May 01 08:36:08 (node:20548) NOTE: The AWS SDK for JavaScript (v2) will be put into maintenance mode in 2023. Please migrate your code to use AWS SDK for JavaScript (v3). For more information, check the migration guide at https://a.co/7PzMCcy (Use node --trace-warnings ... to show where the warning was created) May 01 08:36:13 GET /admin/ 200 67.083 ms - 562 May 01 08:36:13 GET /admin/main.js 304 64.760 ms - - May 01 08:36:13 GET /@signalk/vesselpositions/remoteEntry.js 304 154.940 ms - - May 01 08:36:13 GET /admin/436.js 304 9.732 ms - -

[seamaster101]

Found the fix:
run npm install uuid@^3.3.2 --save-dev
this fixes the problem