Skip to content
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.

Won't build using Node LTS on Debian 10 #77

Open
chrisdlangton opened this issue Apr 9, 2020 · 0 comments
Open

Won't build using Node LTS on Debian 10 #77

chrisdlangton opened this issue Apr 9, 2020 · 0 comments

Comments

@chrisdlangton
Copy link

reproduce using

FROM --platform=amd64 debian:buster-slim
ARG DEBIAN_FRONTEND=noninteractive

WORKDIR /srv/app

RUN apt-get update && \
    apt-get install -y --no-install-recommends -q apt-utils && \
    apt-get install -y --no-install-recommends \
    make git curl wget software-properties-common && \
    curl -sL https://deb.nodesource.com/setup_12.x | bash - && \
    apt-get install -y --no-install-recommends -q nodejs && \
    git clone -q --progress --no-hardlinks https://github.com/tensult/cloud-reports.git && \
    cd /srv/app/cloud-reports && \
    npm run build && \
    npm cache clean --force

CMD [ "bash" ]

for those passing by and not actually caring to reproduce it themselves, the following errors occur;

added 1328 packages from 1044 contributors and audited 33329 packages in 33.383s

26 packages are looking for funding
  run `npm fund` for details

found 88 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

> cloud-reports-final-report@0.1.0 ng /srv/app/cloud-reports/src/reporters/html
> ng "build" "--prod"

Schema validation failed with the following errors:
  Data path ".builders['app-shell']" should have required property 'class'.
Error: Schema validation failed with the following errors:
  Data path ".builders['app-shell']" should have required property 'class'.
    at MergeMapSubscriber.project (/srv/app/cloud-reports/src/reporters/html/node_modules/@angular/cli/node_modules/@angular-devkit/core/src/workspace/workspace.js:173:42)
    at MergeMapSubscriber._tryNext (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/operators/mergeMap.js:122:27)
    at MergeMapSubscriber._next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/operators/mergeMap.js:112:18)
    at MergeMapSubscriber.Subscriber.next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/Subscriber.js:103:18)
    at MergeMapSubscriber.notifyNext (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/operators/mergeMap.js:141:26)
    at InnerSubscriber._next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/InnerSubscriber.js:30:21)
    at InnerSubscriber.Subscriber.next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/Subscriber.js:103:18)
    at MapSubscriber._next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/operators/map.js:92:26)
    at MapSubscriber.Subscriber.next (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/Subscriber.js:103:18)
    at SwitchMapSubscriber.notifyNext (/srv/app/cloud-reports/src/reporters/html/node_modules/rxjs/internal/operators/switchMap.js:122:26)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! cloud-reports-final-report@0.1.0 ng: `ng "build" "--prod"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the cloud-reports-final-report@0.1.0 ng script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-04-09T07_13_19_127Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! cloud-reports@1.6.4 build: `npm install && npm run copy-ejs && tsc && cd src/reporters/html && npm install && npm run ng build --  --prod && cd ../../..`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the cloud-reports@1.6.4 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-04-09T07_13_19_144Z-debug.log

I'm looking for advice to fix it myself, guidance for a PR (i have no clue what's going on here), or acknowledgement of the bug and therefore will be fixed soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant