Created
September 29, 2021 15:09
-
-
Save brotherdust/2fcccf03812f4ac358afeee055728c6b to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| => ERROR [stage-1 5/5] RUN npm install && PATH=$(npm bin):/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin && ng build --prod 81.6s | |
| => [stage-0 8/9] COPY build.go build.go 0.0s | |
| => [stage-0 9/9] RUN go run build.go build 76.7s | |
| => CACHED [stage-2 2/7] WORKDIR /opt/snmpcollector/ 0.0s | |
| => CACHED [stage-2 3/7] RUN apk add --no-cache ca-certificates bash tzdata 0.0s | |
| => CACHED [stage-2 4/7] COPY conf/sample.config.toml ./conf/config.toml 0.0s | |
| => CACHED [stage-2 5/7] RUN addgroup -S -g 472 snmpcol && adduser -S -u 472 -G snmpcol snmpcol && chown -R snmpcol:snmpcol "/opt/snmpcollector/" && mkdir -p "/opt/snmpcollector//data/" && mkdir -p "/opt/snm 0.0s | |
| => CACHED [stage-2 6/7] COPY --from=0 /go/src/github.com/toni-moreno/snmpcollector/bin/snmpcollector ./bin/ 0.0s | |
| ------ | |
| > [stage-1 5/5] RUN npm install && PATH=$(npm bin):/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin && ng build --prod: | |
| #29 5.611 npm WARN deprecated @angular/http@4.3.6: Package no longer supported. Use @angular/common instead, see https://angular.io/guide/deprecations#angularhttp | |
| #29 6.073 npm WARN notice [SECURITY] lodash has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=lodash&version=4.17.21 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 6.845 npm WARN deprecated core-js@2.5.1: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. | |
| #29 9.011 npm WARN deprecated extract-text-webpack-plugin@3.0.0: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin | |
| #29 9.211 npm WARN deprecated html-webpack-plugin@2.30.1: out of support | |
| #29 10.20 npm WARN notice [SECURITY] webpack-dev-server has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=webpack-dev-server&version=2.7.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 10.75 npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. | |
| #29 10.76 npm WARN deprecated core-js@2.6.12: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. | |
| #29 10.86 npm WARN notice [SECURITY] lodash has the following vulnerabilities: 4 high, 2 low. Go here for more details: https://www.npmjs.com/advisories?search=lodash&version=3.10.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 11.29 npm WARN notice [SECURITY] diff has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=diff&version=2.2.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 11.30 npm WARN notice [SECURITY] socket.io has the following vulnerability: 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=socket.io&version=1.7.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 11.60 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 | |
| #29 12.06 npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead: | |
| #29 12.06 npm WARN deprecated npm i nyc | |
| #29 12.06 npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. | |
| #29 13.05 npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. | |
| #29 13.99 npm WARN notice [SECURITY] serialize-javascript has the following vulnerabilities: 1 high, 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=serialize-javascript&version=1.9.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 15.51 npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142 | |
| #29 16.12 npm WARN notice [SECURITY] mime has the following vulnerability: 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=mime&version=1.3.6 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 18.17 npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. | |
| #29 18.33 npm WARN notice [SECURITY] minimist has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=minimist&version=0.0.10 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 18.49 npm WARN notice [SECURITY] braces has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=braces&version=0.1.5 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 18.49 npm WARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=debug&version=2.3.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 19.14 npm WARN deprecated har-validator@5.1.5: this library is no longer supported | |
| #29 19.43 npm WARN notice [SECURITY] https-proxy-agent has the following vulnerabilities: 2 high. Go here for more details: https://www.npmjs.com/advisories?search=https-proxy-agent&version=1.0.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 19.45 npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. | |
| #29 20.01 npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 | |
| #29 20.31 npm WARN deprecated gulp-util@3.0.7: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5 | |
| #29 20.71 npm WARN notice [SECURITY] ssri has the following vulnerability: 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=ssri&version=5.3.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 21.64 npm WARN deprecated har-validator@4.2.1: this library is no longer supported | |
| #29 21.78 npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. | |
| #29 22.06 npm WARN notice [SECURITY] handlebars has the following vulnerabilities: 1 critical, 5 high. Go here for more details: https://www.npmjs.com/advisories?search=handlebars&version=1.3.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 22.97 npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. | |
| #29 23.62 npm WARN notice [SECURITY] yargs-parser has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=yargs-parser&version=4.2.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 23.90 npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. | |
| #29 24.65 npm WARN notice [SECURITY] yargs-parser has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=yargs-parser&version=7.0.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 24.99 npm WARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=debug&version=2.2.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 25.05 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 | |
| #29 25.26 npm WARN notice [SECURITY] ws has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=ws&version=1.1.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 25.70 npm WARN notice [SECURITY] adm-zip has the following vulnerabilities: 2 high. Go here for more details: https://www.npmjs.com/advisories?search=adm-zip&version=0.4.4 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 27.36 npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash. | |
| #29 27.47 npm WARN notice [SECURITY] js-yaml has the following vulnerabilities: 1 high, 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=js-yaml&version=3.7.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 27.84 npm WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=hoek&version=2.16.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 27.86 npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). | |
| #29 27.92 npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. | |
| #29 27.95 npm WARN notice [SECURITY] cryptiles has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=cryptiles&version=2.0.5 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 27.97 npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). | |
| #29 28.01 npm WARN notice [SECURITY] uglify-js has the following vulnerabilities: 2 low. Go here for more details: https://www.npmjs.com/advisories?search=uglify-js&version=2.3.6 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 28.19 npm WARN notice [SECURITY] xmldom has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=xmldom&version=0.1.31 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 28.19 npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated | |
| #29 28.23 npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0 | |
| #29 28.62 npm WARN notice [SECURITY] braces has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=braces&version=1.8.5 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 29.33 npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). | |
| #29 30.18 npm WARN notice [SECURITY] mem has the following vulnerability: 1 low. Go here for more details: https://www.npmjs.com/advisories?search=mem&version=1.1.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 30.30 npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. | |
| #29 30.42 npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. | |
| #29 31.07 npm WARN notice [SECURITY] parsejson has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=parsejson&version=0.0.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 31.13 npm WARN notice [SECURITY] xmlhttprequest-ssl has the following vulnerabilities: 1 critical, 1 high. Go here for more details: https://www.npmjs.com/advisories?search=xmlhttprequest-ssl&version=1.5.3 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 32.94 npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated | |
| #29 34.24 npm WARN notice [SECURITY] glob-parent has the following vulnerability: 1 moderate. Go here for more details: https://www.npmjs.com/advisories?search=glob-parent&version=3.1.0 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 36.01 npm WARN notice [SECURITY] set-value has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=set-value&version=2.0.1 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. | |
| #29 67.00 | |
| #29 67.00 > node-sass@4.14.1 install /usr/src/app/node_modules/node-sass | |
| #29 67.00 > node scripts/install.js | |
| #29 67.00 | |
| #29 67.33 Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/linux_musl-x64-57_binding.node | |
| #29 68.47 Download complete | |
| #29 68.48 Binary saved to /usr/src/app/node_modules/node-sass/vendor/linux_musl-x64-57/binding.node | |
| #29 68.49 Caching binary to /root/.npm/node-sass/4.14.1/linux_musl-x64-57_binding.node | |
| #29 68.55 | |
| #29 68.55 > wd@1.14.0 install /usr/src/app/node_modules/wd | |
| #29 68.55 > node scripts/build-browser-scripts | |
| #29 68.55 | |
| #29 68.79 | |
| #29 68.79 > ejs@2.7.4 postinstall /usr/src/app/node_modules/ejs | |
| #29 68.79 > node ./postinstall.js | |
| #29 68.79 | |
| #29 68.86 Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/) | |
| #29 68.86 | |
| #29 69.04 | |
| #29 69.04 > uglifyjs-webpack-plugin@0.4.6 postinstall /usr/src/app/node_modules/uglifyjs-webpack-plugin | |
| #29 69.04 > node lib/post_install.js | |
| #29 69.04 | |
| #29 69.13 | |
| #29 69.13 > sauce-connect-launcher@1.3.2 postinstall /usr/src/app/node_modules/sauce-connect-launcher | |
| #29 69.13 > node scripts/install.js || nodejs scripts/install.js | |
| #29 69.13 | |
| #29 69.21 | |
| #29 69.21 > node-sass@4.14.1 postinstall /usr/src/app/node_modules/node-sass | |
| #29 69.21 > node scripts/build.js | |
| #29 69.21 | |
| #29 69.33 Binary found at /usr/src/app/node_modules/node-sass/vendor/linux_musl-x64-57/binding.node | |
| #29 69.33 Testing binary | |
| #29 69.40 Binary is fine | |
| #29 71.08 npm notice created a lockfile as package-lock.json. You should commit this file. | |
| #29 71.08 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): | |
| #29 71.08 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) | |
| #29 71.08 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents): | |
| #29 71.08 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) | |
| #29 71.08 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents): | |
| #29 71.08 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) | |
| #29 71.08 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/karma/node_modules/chokidar/node_modules/fsevents): | |
| #29 71.09 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) | |
| #29 71.09 npm WARN @angular-devkit/schematics@0.0.52 requires a peer of @angular-devkit/core@0.0.29 but none is installed. You must install peer dependencies yourself. | |
| #29 71.09 npm WARN @schematics/angular@0.0.49 requires a peer of @angular-devkit/schematics@0.0.34 but none is installed. You must install peer dependencies yourself. | |
| #29 71.09 | |
| #29 71.09 added 1479 packages in 69.845s | |
| #29 75.22 Date: 2021-09-29T14:40:31.396Z | |
| #29 81.43 Hash: 74bbdf7c8abcfdeec1fc | |
| #29 81.43 Time: 6213ms | |
| #29 81.43 chunk {0} styles.8e83b572b23a036cc343.bundle.css (styles) 116 kB {2} [initial] [rendered] | |
| #29 81.43 chunk {1} main.ac12cef0639b0265a042.bundle.js (main) 84 bytes [initial] [rendered] | |
| #29 81.43 chunk {2} inline.d1875e78fa413b490c01.bundle.js (inline) 1.42 kB [entry] [rendered] | |
| #29 81.43 | |
| #29 81.43 ERROR in Error: Cannot determine the module for class SwaggerUiComponent in /usr/src/app/src/swagger-ui/swagger-ui.component.ts! Add SwaggerUiComponent to the NgModule to fix it. | |
| #29 81.43 at syntaxError (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:1725:34) | |
| #29 81.43 at analyzeAndValidateNgModules (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:24139:15) | |
| #29 81.43 at AotCompiler.analyzeModulesAsync (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:23772:46) | |
| #29 81.43 at CodeGenerator.codegen (/usr/src/app/node_modules/@angular/compiler-cli/src/codegen.js:32:14) | |
| #29 81.43 at Function.NgTools_InternalApi_NG_2.codeGen (/usr/src/app/node_modules/@angular/compiler-cli/src/ngtools_api.js:73:30) | |
| #29 81.43 at _donePromise.Promise.resolve.then (/usr/src/app/node_modules/@ngtools/webpack/src/plugin.js:386:44) | |
| #29 81.43 at <anonymous> | |
| ------ | |
| executor failed running [/bin/sh -c npm install && PATH=$(npm bin):$PATH && ng build --prod]: exit code: 1 |
Are you sure you has been reverted to tje rigth commit?. Tbere is something wrong in your local repo . At this point of time there is not any SwaggerUiComponent in snmpcollector yet.
I'm recreating myself the image ok when reverting these commits back
Yeah I started with a completely clean repository. I actually deleted the old one, downloaded fresh copy from GitHub directly then apply the command you mentioned.
I will try starting fresh again this afternoon when I return to my office.
Just type git reset 6e6eb3233be8ef91b8989298c4df081d96bd51e9 and check with git log you have not swagger commits anymore.
I'm trying to reproduce your logs with the last commit , but I'm not able to do it!!.
this is my output log.
added 1480 packages in 57.098s
10% building modules 7/8 modules 1 active ..._modules/css-loader/lib/url/escape.jsTemplate parse warnings:
The <template> element is deprecated. Use <ng-template> instead ("
[WARNING ->]<template [ngIf]="!isClosed">
<div [class]="'alert alert-' + type" role="alert" [ngClass]="classes""): ng:///usr/src/app/node_modules/ngx-bootstrap/alert/alert.component.d.ts.AlertComponent.html@1:0
94% asset optimization(node:76) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token: name (n)
at JS_Parse_Error.get (eval at <anonymous> (/usr/src/app/node_modules/webpack-concat-plugin/node_modules/uglify-js/tools/node.js:27:1), <anonymous>:86:23)
at emitWarning (internal/process/promises.js:65:36)
at emitPendingUnhandledRejections (internal/process/promises.js:109:11)
at process._tickCallback (internal/process/next_tick.js:189:7)
(node:76) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:76) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Did you any changes in the package.json or node version ?
I've also looking for you error and it's similar to this other ( https://stackoverflow.com/questions/46882983/angular-ng-build-prod-cannot-determine-the-module-for-class-add-class-to-th) , perhaps could be fixed if you add a export section in the @NgModule (https://github.com/toni-moreno/snmpcollector/blob/master/src/main.module.ts) ????
exports: [
SwaggerUiComponent,
]
Could you tell me what changes did you in node or package.json to get this error ( better than mine)
29 81.43 ERROR in Error: Cannot determine the module for class SwaggerUiComponent in /usr/src/app/src/swagger-ui/swagger-ui.component.ts! Add SwaggerUiComponent to the NgModule to fix it.
#29 81.43 at syntaxError (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:1725:34)
#29 81.43 at analyzeAndValidateNgModules (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:24139:15)
#29 81.43 at AotCompiler.analyzeModulesAsync (/usr/src/app/node_modules/@angular/compiler/bundles/compiler.umd.js:23772:46)
#29 81.43 at CodeGenerator.codegen (/usr/src/app/node_modules/@angular/compiler-cli/src/codegen.js:32:14)
#29 81.43 at Function.NgTools_InternalApi_NG_2.codeGen (/usr/src/app/node_modules/@angular/compiler-cli/src/ngtools_api.js:73:30)
#29 81.43 at _donePromise.Promise.resolve.then (/usr/src/app/node_modules/@ngtools/webpack/src/plugin.js:386:44)
#29 81.43 at <anonymous>
No changes at all. I don't know why it was doing that. Maybe something to
do with Git.
Jarad Olson
…On Thu, Sep 30, 2021 at 12:11 PM Toni Moreno ***@***.***> wrote:
***@***.**** commented on this gist.
------------------------------
Could you tell me what changes did you in node or package.json to get this
error ( better than mine)
29 81.43 ERROR in Error: Cannot determine the module for class SwaggerUiComponent in /usr/src/app/src/swagger-ui/swagger-ui.component.ts! Add SwaggerUiComponent to the NgModule to fix it.
#29 81.43 at syntaxError ***@***.***/compiler/bundles/compiler.umd.js:1725:34)
#29 81.43 at analyzeAndValidateNgModules ***@***.***/compiler/bundles/compiler.umd.js:24139:15)
#29 81.43 at AotCompiler.analyzeModulesAsync ***@***.***/compiler/bundles/compiler.umd.js:23772:46)
#29 81.43 at CodeGenerator.codegen ***@***.***/compiler-cli/src/codegen.js:32:14)
#29 81.43 at Function.NgTools_InternalApi_NG_2.codeGen ***@***.***/compiler-cli/src/ngtools_api.js:73:30)
#29 81.43 at _donePromise.Promise.resolve.then ***@***.***/webpack/src/plugin.js:386:44)
#29 81.43 at <anonymous>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://gist.github.com/2fcccf03812f4ac358afeee055728c6b#gistcomment-3912758>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPOHWE4D4PKWGZHBVIZDCLUESR5BANCNFSM5FASIAJQ>
.
Are you building at your local desktop? What node version do you have installed?
I’m building with Docker, so whatever version of node is being used in the Dockerfile. I think that’s…. 8.10, right?
I got it to build earlier today. See the issue on GitHub
…Sent from my iPhone
On Sep 30, 2021, at 13:15, Toni Moreno ***@***.***> wrote:
***@***.*** commented on this gist.
Are you building at your local desktop? What node version do you have installed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are you sure you has been reverted to tje rigth commit?. Tbere is something wrong in your local repo . At this point of time there is not any SwaggerUiComponent in snmpcollector yet.
I'm recreating myself the image ok when reverting these commits back