Skip to main content

Deploy details

Published deploy for repsymo

@netlify/angular-runtime failed but the deploy was able to complete.
Merge pull request #67 from repsymo/rsm/ops Update deps that were causing issues

Production: rsm/dev@6c20502

Deploy summary

  • warning

    Plugin "@netlify/angular-runtime" failed

    Error: Could not parse contents of angular.json

    In "onPreBuild" event in "@netlify/angular-runtime" from Netlify app

  • warning

    Runtime "@netlify/angular-runtime" failed

    Error: Could not parse contents of angular.json

    In "onPreBuild" event in "@netlify/angular-runtime" from Netlify app

  • info

    Build time: 1m 28s. Total deploy time: 1m 28s

    Build started at 12:23:28 AM and ended at 12:24:56 AM. Learn more about build minutes

Deploy log

Initializing

Complete
12:21:54 AM: Waiting for other deploys from your team to complete. Check the queue: https://app.netlify.com/teams/tobiasbriones/builds
12:23:13 AM: Build ready to start
12:23:28 AM: build-image version: fcb0c1b3ada6d25c1cb58e8bc514f5f23cc14f15 (focal)
12:23:28 AM: buildbot version: 2003611e3bb7348fdcaaf48430d0722f44f1cda4
12:23:28 AM: Fetching cached dependencies
12:23:28 AM: Failed to fetch cache, continuing with build
12:23:28 AM: Starting to prepare the repo for build
12:23:28 AM: No cached dependencies found. Cloning fresh repo
12:23:28 AM: git clone --filter=blob:none https://github.com/repsymo/repsymo---mvp
12:23:29 AM: Preparing Git Reference refs/heads/rsm/dev
12:23:32 AM: Starting to install dependencies
12:23:34 AM: Python version set to 3.8
12:23:35 AM: Attempting Ruby version 2.7.2, read from environment
12:23:36 AM: Using Ruby version 2.7.2
12:23:36 AM: Started restoring cached go cache
12:23:36 AM: Finished restoring cached go cache
12:23:38 AM: go version go1.19.13 linux/amd64
12:23:39 AM: Using PHP version 8.0
12:23:41 AM: Downloading and installing node v18.20.1...
12:23:42 AM: Computing checksum with sha256sum
12:23:42 AM: Checksums matched!
12:23:45 AM: Now using node v18.20.1 (npm v10.5.0)
12:23:45 AM: Enabling Node.js Corepack
12:23:45 AM: Started restoring cached build plugins
12:23:45 AM: Finished restoring cached build plugins
12:23:45 AM: Started restoring cached corepack dependencies
12:23:45 AM: Finished restoring cached corepack dependencies
12:23:45 AM: No npm workspaces detected
12:23:45 AM: Started restoring cached node modules
12:23:45 AM: Finished restoring cached node modules
12:23:46 AM: Installing npm packages using npm version 10.5.0
12:23:58 AM: npm WARN deprecated har-validator@5.1.5: this library is no longer supported
12:24:00 AM: 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.
12:24:00 AM: npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
12:24:01 AM: npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
12:24:02 AM: npm WARN deprecated @babel/polyfill@7.7.0: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
12:24:05 AM: npm WARN deprecated protractor@7.0.0: We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular
12:24:10 AM: npm WARN deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:19 AM: npm WARN deprecated core-js@2.6.11: core-js@<3.4 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.
12:24:23 AM: added 1287 packages, and audited 1288 packages in 37s
12:24:23 AM: 114 packages are looking for funding
12:24:23 AM: run `npm fund` for details
12:24:23 AM: 23 vulnerabilities (1 low, 20 moderate, 1 high, 1 critical)
12:24:23 AM: To address issues that do not require attention, run:
12:24:23 AM: npm audit fix
12:24:23 AM: To address all issues possible (including breaking changes), run:
12:24:23 AM: npm audit fix --force
12:24:23 AM: Some issues need review, and may require choosing
12:24:23 AM: a different dependency.
12:24:23 AM: Run `npm audit` for details.
12:24:23 AM: npm packages installed
12:24:23 AM: Successfully installed dependencies
12:24:24 AM: Starting build script
12:24:27 AM: Detected 0 framework(s)
12:24:27 AM: Section completed: initializing

Building

Complete
12:24:29 AM: Netlify Build
12:24:29 AM: ────────────────────────────────────────────────────────────────
12:24:29 AM:
12:24:29 AM: ❯ Version
12:24:29 AM: @netlify/build 29.39.0
12:24:29 AM:
12:24:29 AM: ❯ Flags
12:24:29 AM: baseRelDir: true
12:24:29 AM: buildId: 660f4422bf06920008f72667
12:24:29 AM: deployId: 660f4422bf06920008f72669
12:24:29 AM:
12:24:29 AM: ❯ Current directory
12:24:29 AM: /opt/build/repo
12:24:29 AM:
12:24:29 AM: ❯ Config file
12:24:29 AM: /opt/build/repo/netlify.toml
12:24:29 AM:
12:24:29 AM: ❯ Context
12:24:29 AM: production
12:24:29 AM:
12:24:29 AM: ❯ Installing plugins
12:24:29 AM: - @netlify/angular-runtime@2.0.6
12:24:30 AM:
12:24:30 AM: ❯ Loading plugins
12:24:30 AM: - @netlify/angular-runtime@2.0.6 from Netlify app
12:24:32 AM:
12:24:32 AM: @netlify/angular-runtime (onPreBuild event)
12:24:32 AM: ────────────────────────────────────────────────────────────────
12:24:32 AM: ​
12:24:32 AM:
12:24:32 AM: Plugin "@netlify/angular-runtime" failed
12:24:32 AM: ────────────────────────────────────────────────────────────────
12:24:32 AM: ​
12:24:32 AM: Error message
12:24:32 AM: Error: Could not parse contents of angular.json
12:24:32 AM: ​
12:24:32 AM: Plugin details
12:24:32 AM: Package: @netlify/angular-runtime
12:24:32 AM: Version: 2.0.6
12:24:32 AM: ​
12:24:32 AM: Error location
12:24:32 AM: In "onPreBuild" event in "@netlify/angular-runtime" from Netlify app
12:24:32 AM: ​
12:24:32 AM: Resolved config
12:24:32 AM: build:
12:24:32 AM: command: npm run build
12:24:32 AM: commandOrigin: ui
12:24:32 AM: publish: /opt/build/repo/dist
12:24:32 AM: publishOrigin: ui
12:24:32 AM: plugins:
12:24:32 AM: - inputs: {}
12:24:32 AM: origin: ui
12:24:32 AM: package: "@netlify/angular-runtime"
12:24:32 AM: redirects:
12:24:32 AM: - from: /*
status: 200
to: /
redirectsOrigin: config
12:24:32 AM: Build command from Netlify app
12:24:32 AM: ────────────────────────────────────────────────────────────────
12:24:32 AM: ​
12:24:32 AM: $ npm run build
12:24:33 AM: > repsymo@0.1.0-dev build
12:24:33 AM: > ng build --configuration production
12:24:34 AM: One or more browsers which are configured in the project"s Browserslist configuration will be ignored as ES5 output is not supported by the Angular CLI.
Ignored browsers: kaios 2.5, op_mini all
12:24:34 AM: - Generating browser application bundles (phase: setup)...
12:24:55 AM: Browser application bundle generation complete.
12:24:55 AM: Browser application bundle generation complete.
12:24:55 AM: - Copying assets...
12:24:55 AM: Copying assets complete.
12:24:55 AM: - Generating index html...
12:24:55 AM: Index html generation complete.
12:24:55 AM: - Generating service worker...
12:24:55 AM: Service worker generation complete.
12:24:55 AM:
12:24:55 AM: Initial chunk files | Names | Raw size | Estimated transfer size
12:24:55 AM: main.0478feba2450e235.js | main | 332.37 kB | 82.30 kB
12:24:55 AM: polyfills.785dc2318de7c50c.js | polyfills | 33.39 kB | 10.78 kB
12:24:55 AM: styles.1169b3306bd8b1e8.css | styles | 2.59 kB | 730 bytes
12:24:55 AM: runtime.55f56d7f760a27c4.js | runtime | 1.04 kB | 595 bytes
12:24:55 AM:
12:24:55 AM: | Initial total | 369.39 kB | 94.37 kB
12:24:55 AM:
12:24:55 AM: Build at: 2024-04-05T00:24:55.656Z - Hash: 38059f66313a1fb0 - Time: 20515ms
12:24:55 AM: ​
12:24:55 AM: (build.command completed in 22.8s)
12:24:55 AM:
12:24:56 AM: (Netlify Build completed in 26.8s)
12:25:17 AM: Section completed: building
12:25:21 AM: Finished processing build request in 1m53.604s

Deploying

Complete
12:24:55 AM: Deploy site
12:24:55 AM: ────────────────────────────────────────────────────────────────
12:24:55 AM: ​
12:24:55 AM: Starting to deploy site from "dist"
12:24:55 AM: Calculating files to upload
12:24:56 AM: 1 new files to upload
12:24:56 AM: 0 new functions to upload
12:24:56 AM: Section completed: deploying
12:24:56 AM: Site deploy was successfully initiated
12:24:56 AM: ​
12:24:56 AM: (Deploy site completed in 327ms)

Cleanup

Complete
12:24:56 AM: Netlify Build Complete
12:24:56 AM: ────────────────────────────────────────────────────────────────
12:24:56 AM: ​
12:24:56 AM: Caching artifacts
12:24:56 AM: Started saving node modules
12:24:56 AM: Finished saving node modules
12:24:56 AM: Started saving build plugins
12:24:56 AM: Finished saving build plugins
12:24:56 AM: Started saving corepack cache
12:24:56 AM: Finished saving corepack cache
12:24:56 AM: Started saving pip cache
12:24:56 AM: Finished saving pip cache
12:24:56 AM: Started saving emacs cask dependencies
12:24:56 AM: Finished saving emacs cask dependencies
12:24:56 AM: Started saving maven dependencies
12:24:56 AM: Finished saving maven dependencies
12:24:56 AM: Started saving boot dependencies
12:24:57 AM: Finished saving boot dependencies
12:24:57 AM: Started saving rust rustup cache
12:24:57 AM: Finished saving rust rustup cache
12:24:57 AM: Started saving go dependencies
12:24:57 AM: Finished saving go dependencies
12:25:17 AM: Build script success
12:25:20 AM: Uploading Cache of size 187.7MB
12:25:21 AM: Section completed: cleanup

Post-processing

Complete
12:24:56 AM: Starting post processing
12:24:56 AM: Skipping form detection
12:24:56 AM: Post processing - header rules
12:24:56 AM: Post processing - redirect rules
12:24:56 AM: Post processing done
12:24:56 AM: Section completed: postprocessing
12:24:56 AM: Site is live ✨