System info: OS: Debian GNU/Linux 12.11 (updated via apt update && apt upgrade)
Node.js: tried v18.19.0 and v22.17.0 (via n)
npm: v9.2.0 and v10.9.2
Angular CLI: tried both global and local installs (v13.x, latest, etc.)
Clean environment: cloned fresh from GitHub into /opt/xmworkers
What happened:
I tried to build the project according to the standard npm install → ng build --configuration production process, but ran into a complete mess of dependency issues:
Initial npm install failed due to peerDependency conflicts (jasmine-core, karma-jasmine-html-reporter, etc.)
Tried --legacy-peer-deps → got 404 for @sweetalert2/theme-borderless@^4.0.3
After manually removing that from package.json, install went through
Build failed with Class extends value undefined is not a constructor or null in webpack/lib/MainTemplate.js
Updated Node.js from v18 → v22 → still the same issue
Tried pinning Angular CLI to v13.3.12 → not found / not installable via npm
Tried rebuilding node_modules multiple times with various combinations → still failed
All this was done on a fresh, minimal, updated Debian 12.11 system with only the required tools installed (nodejs, npm, @angular/cli etc.).
Expected behavior:
I expected to be able to build the project after npm install, or at least get a clean dependency tree that works with a common Node.js version (18 or 22).
Actual result:
After an hour of trying various versions, workarounds, flags, and patches – the project still cannot be built due to outdated/incompatible dependencies and broken peer resolution.
💡 Suggested solution
Please either:
Provide a dist/ ZIP for users who just want to run the frontend (e.g. via python3 -m http.server), or
Update package.json and package-lock.json to reflect a working dependency tree (with known working versions), and ideally document the compatible Node/npm versions.
🙏 Thank you
I really like the idea and look of this project, but the current build process is extremely frustrating for non-Node developers and nearly impossible to fix without hours of trial & error. A prebuilt release or a working Dockerfile would go a long way.
System info: OS: Debian GNU/Linux 12.11 (updated via apt update && apt upgrade)
Node.js: tried v18.19.0 and v22.17.0 (via n)
npm: v9.2.0 and v10.9.2
Angular CLI: tried both global and local installs (v13.x, latest, etc.)
Clean environment: cloned fresh from GitHub into /opt/xmworkers
What happened:
I tried to build the project according to the standard npm install → ng build --configuration production process, but ran into a complete mess of dependency issues:
Initial npm install failed due to peerDependency conflicts (jasmine-core, karma-jasmine-html-reporter, etc.)
Tried --legacy-peer-deps → got 404 for @sweetalert2/theme-borderless@^4.0.3
After manually removing that from package.json, install went through
Build failed with Class extends value undefined is not a constructor or null in webpack/lib/MainTemplate.js
Updated Node.js from v18 → v22 → still the same issue
Tried pinning Angular CLI to v13.3.12 → not found / not installable via npm
Tried rebuilding node_modules multiple times with various combinations → still failed
All this was done on a fresh, minimal, updated Debian 12.11 system with only the required tools installed (nodejs, npm, @angular/cli etc.).
Expected behavior:
I expected to be able to build the project after npm install, or at least get a clean dependency tree that works with a common Node.js version (18 or 22).
Actual result:
After an hour of trying various versions, workarounds, flags, and patches – the project still cannot be built due to outdated/incompatible dependencies and broken peer resolution.
💡 Suggested solution
Please either:
Provide a dist/ ZIP for users who just want to run the frontend (e.g. via python3 -m http.server), or
Update package.json and package-lock.json to reflect a working dependency tree (with known working versions), and ideally document the compatible Node/npm versions.
🙏 Thank you
I really like the idea and look of this project, but the current build process is extremely frustrating for non-Node developers and nearly impossible to fix without hours of trial & error. A prebuilt release or a working Dockerfile would go a long way.