heldcraft
commented
7 months ago you need to change in the build script line 5 from: RUN npm install -g @angular/cli \ to: RUN npm install -g @angular/cli@8 \
Open Lightwel opened 10 months ago
heldcraft
commented
7 months ago you need to change in the build script line 5 from: RUN npm install -g @angular/cli \ to: RUN npm install -g @angular/cli@8 \
Hi - nodejs has been updated since this package was originally released. Despite installing nodejs 20, I am getting errors which I cannot fix.
This is the latest error message pointing to a failed dependency which is listed in the original package:
`ubuntu@ubuntu:~/GIT/sdrangelcli$ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: @angular-devkit/build-angular@17.0.1 npm ERR! Found: @angular/compiler-cli@12.2.2 npm ERR! node_modules/@angular/compiler-cli npm ERR! dev @angular/compiler-cli@"^12.2.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer @angular/compiler-cli@"^17.0.0" from @angular-devkit/build-angular@17.0.1 npm ERR! node_modules/@angular-devkit/build-angular npm ERR! dev @angular-devkit/build-angular@"^17.0.1" from the root project npm ERR! npm ERR! Conflicting peer dependency: @angular/compiler-cli@17.0.3 npm ERR! node_modules/@angular/compiler-cli npm ERR! peer @angular/compiler-cli@"^17.0.0" from @angular-devkit/build-angular@17.0.1 npm ERR! node_modules/@angular-devkit/build-angular npm ERR! dev @angular-devkit/build-angular@"^17.0.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /home/ubuntu/.npm/_logs/2023-11-17T22_57_00_110Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-17T22_57_00_110Z-debug-0.log ` While sdrangelcli might be an 'edge' use case, it would be great to have an updated git package to work from.
PS I have tried the docker build, but that is also failing on the rpi and tbh docker is a learning curve I would rather decline. If docker is the only way to go, then the portainer build instructions need updating and the docker hub repositories, at least as of last night, lack manifests and cannot be downloaded. Also, some instruction on how to assemble the component downloads would be helpful.
In admiration and hope : ..
Tks R