Wont Build or start from source, or even just the binary.

[blaze-developer]

When building the code using npm install, errors are thrown.

root@berry:~/FlashForgeWebUI-main# npm run build

> flashforge-webui@1.0.0 build
> npm run build:backend && npm run build:webui


> flashforge-webui@1.0.0 build:backend
> tsc

src/services/SpoolmanService.ts:74:21 - error TS2339: Property 'ok' does not exist on type 'Response'.

74       if (!response.ok) {
                       ~~

src/services/SpoolmanService.ts:75:42 - error TS2339: Property 'status' does not exist on type 'Response'.

75         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                            ~~~~~~

src/services/SpoolmanService.ts:75:62 - error TS2339: Property 'statusText' does not exist on type 'Response'.

75         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                                                ~~~~~~~~~~

src/services/SpoolmanService.ts:78:30 - error TS2339: Property 'json' does not exist on type 'Response'.

78       return (await response.json()) as SpoolResponse[];
                                ~~~~

src/services/SpoolmanService.ts:100:21 - error TS2339: Property 'ok' does not exist on type 'Response'.

100       if (!response.ok) {
                        ~~

src/services/SpoolmanService.ts:101:22 - error TS2339: Property 'status' does not exist on type 'Response'.

101         if (response.status === 404) {
                         ~~~~~~

src/services/SpoolmanService.ts:104:42 - error TS2339: Property 'status' does not exist on type 'Response'.

104         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                             ~~~~~~

src/services/SpoolmanService.ts:104:62 - error TS2339: Property 'statusText' does not exist on type 'Response'.

104         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                                                 ~~~~~~~~~~

src/services/SpoolmanService.ts:107:30 - error TS2339: Property 'json' does not exist on type 'Response'.

107       return (await response.json()) as SpoolResponse;
                                 ~~~~

src/services/SpoolmanService.ts:143:21 - error TS2339: Property 'ok' does not exist on type 'Response'.

143       if (!response.ok) {
                        ~~

src/services/SpoolmanService.ts:144:22 - error TS2339: Property 'status' does not exist on type 'Response'.

144         if (response.status === 404) {
                         ~~~~~~

src/services/SpoolmanService.ts:147:42 - error TS2339: Property 'status' does not exist on type 'Response'.

147         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                             ~~~~~~

src/services/SpoolmanService.ts:147:62 - error TS2339: Property 'statusText' does not exist on type 'Response'.

147         throw new Error(`HTTP ${response.status}: ${response.statusText}`);
                                                                 ~~~~~~~~~~

src/services/SpoolmanService.ts:150:30 - error TS2339: Property 'json' does not exist on type 'Response'.

150       return (await response.json()) as SpoolResponse;
                                 ~~~~

src/services/SpoolmanService.ts:171:29 - error TS2339: Property 'ok' does not exist on type 'Response'.

171         connected: response.ok,
                                ~~

src/services/SpoolmanService.ts:172:25 - error TS2339: Property 'ok' does not exist on type 'Response'.

172         error: response.ok ? undefined : `HTTP ${response.status}`,
                            ~~

src/services/SpoolmanService.ts:172:59 - error TS2339: Property 'status' does not exist on type 'Response'.

172         error: response.ok ? undefined : `HTTP ${response.status}`,
                                                              ~~~~~~


Found 17 errors in the same file, starting at: src/services/SpoolmanService.ts:74

When running npm run start, other errors:

root@berry:~/FlashForgeWebUI-main# npm run start

> flashforge-webui@1.0.0 start
> node dist/index.js

node:internal/modules/cjs/loader:1423
  throw err;
  ^

Error: Cannot find module 'escape-html'
Require stack:
- /root/FlashForgeWebUI-main/node_modules/finalhandler/index.js
- /root/FlashForgeWebUI-main/node_modules/express/lib/application.js
- /root/FlashForgeWebUI-main/node_modules/express/lib/express.js
- /root/FlashForgeWebUI-main/node_modules/express/index.js
- /root/FlashForgeWebUI-main/dist/webui/server/WebUIManager.js
- /root/FlashForgeWebUI-main/dist/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1420:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1058:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1063:22)
    at Module._load (node:internal/modules/cjs/loader:1226:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)
    at Module.require (node:internal/modules/cjs/loader:1503:12)
    at require (node:internal/modules/helpers:152:16)
    at Object.<anonymous> (/root/FlashForgeWebUI-main/node_modules/finalhandler/index.js:16:18)
    at Module._compile (node:internal/modules/cjs/loader:1760:14) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/root/FlashForgeWebUI-main/node_modules/finalhandler/index.js',
    '/root/FlashForgeWebUI-main/node_modules/express/lib/application.js',
    '/root/FlashForgeWebUI-main/node_modules/express/lib/express.js',
    '/root/FlashForgeWebUI-main/node_modules/express/index.js',
    '/root/FlashForgeWebUI-main/dist/webui/server/WebUIManager.js',
    '/root/FlashForgeWebUI-main/dist/index.js'
  ]
}

I also cant run the linux-arm64 binary:

root@berry:~# ./flashforge-webui-linux-arm64.bin 
pkg/prelude/bootstrap.js:1872
      throw error;
      ^

Error: Cannot find module '/snapshot/FlashForgeWebUI/node_modules/axios/dist/node/axios.cjs'
1) If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.
    at createEsmNotFoundErr (node:internal/modules/cjs/loader:1262:15)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1250:15)
    at resolveExports (node:internal/modules/cjs/loader:634:14)
    at Module._findPath (node:internal/modules/cjs/loader:724:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1211:27)
    at Function._resolveFilename (pkg/prelude/bootstrap.js:1955:46)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Module.require (node:internal/modules/cjs/loader:1311:19)
    at Module.require (pkg/prelude/bootstrap.js:1851:31)
    at require (node:internal/modules/helpers:179:18) {
  code: 'MODULE_NOT_FOUND',
  path: '/snapshot/FlashForgeWebUI/node_modules/axios/package.json',
  pkg: true
}

Node.js v20.18.0

[GhostTypes]

Hello, sorry for the late response - I don't yet have a Linux setup / a Pi to test on

I checked by cloning the repo to a new folder and don't have those errors with npm install, but perhaps it's platform specific.

npm install

Regarding npm run start , the correct command would be

npm run dev

I'm not entirely sure yet why axios (and other deps) were not included , it appears to have affected all the Linux builds
I've just pushed some changes 07aaa64 here to address this and will be looking into this further