6:30:43 PM: Build ready to start 6:30:45 PM: build-image version: 653805ca4a64301556e56dc4b321ef8fc20cbb7c 6:30:45 PM: build-image tag: v...

Rodrigo Angel Zucchini

Rodrigo Angel Zucchini

Pregunta
studenthace 4 años

6:30:43 PM: Build ready to start

6:30:45 PM: build-image version: 653805ca4a64301556e56dc4b321ef8fc20cbb7c

6:30:45 PM: build-image tag: v3.8.2

6:30:45 PM: buildbot version: b63d1717a02404f31eb4f9710e846c40c86af045

6:30:45 PM: Fetching cached dependencies

6:30:45 PM: Failed to fetch cache, continuing with build

6:30:45 PM: Starting to prepare the repo for build

6:30:45 PM: No cached dependencies found. Cloning fresh repo

6:30:45 PM: git clone https://github.com/rodrigozucchini/curso-webpack

6:30:46 PM: Preparing Git Reference refs/heads/main

6:30:46 PM: Parsing package.json dependencies

6:30:47 PM: Starting build script

6:30:47 PM: Installing dependencies

6:30:47 PM: Python version set to 2.7

6:30:48 PM: v12.18.0 is already installed.

6:30:49 PM: Now using node v12.18.0 (npm v6.14.4)

6:30:49 PM: Started restoring cached build plugins

6:30:49 PM: Finished restoring cached build plugins

6:30:49 PM: Attempting ruby version 2.7.2, read from environment

6:30:50 PM: Using ruby version 2.7.2

6:30:51 PM: Using PHP version 5.6

6:30:51 PM: Started restoring cached node modules

6:30:51 PM: Finished restoring cached node modules

6:30:51 PM: Installing NPM modules using NPM version 6.14.4

6:31:00 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I’ll try to do my best with it!

added 434 packages from 245 contributors and audited 434 packages in 7.972s

6:31:00 PM: 53 packages are looking for funding

6:31:00 PM: run

npm fund
for details

6:31:00 PM: found 0 vulnerabilities

6:31:00 PM: NPM modules installed

6:31:00 PM: Started restoring cached go cache

6:31:00 PM: Finished restoring cached go cache

6:31:00 PM: go version go1.14.4 linux/amd64

6:31:00 PM: go version go1.14.4 linux/amd64

6:31:00 PM: Installing missing commands

6:31:00 PM: Verify run directory

6:31:01 PM: ​

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: Netlify Build

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: ​

6:31:01 PM: ❯ Version

6:31:01 PM: @netlify/build 17.1.1

6:31:01 PM: ​

6:31:01 PM: ❯ Flags

6:31:01 PM: deployId: 61007b03df0e333d873278b8

6:31:01 PM: ​

6:31:01 PM: ❯ Current directory

6:31:01 PM: /opt/build/repo

6:31:01 PM: ​

6:31:01 PM: ❯ Config file

6:31:01 PM: /opt/build/repo/netlify.toml

6:31:01 PM: ​

6:31:01 PM: ❯ Context

6:31:01 PM: production

6:31:01 PM: ​

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: 1. build.command from netlify.toml

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: ​

6:31:01 PM: $ npm run build

6:31:01 PM: > js-portfolio@1.0.0 build /opt/build/repo

6:31:01 PM: > webpack --mode production --config webpack.config.js

6:31:01 PM: sh: 1: webpack: not found

6:31:01 PM: npm ERR! code ELIFECYCLE

6:31:01 PM: npm ERR! syscall spawn

6:31:01 PM: npm ERR! file sh

6:31:01 PM: npm ERR! errno ENOENT

6:31:01 PM: npm ERR! js-portfolio@1.0.0 build:

webpack --mode production --config webpack.config.js

6:31:01 PM: npm ERR! spawn ENOENT

6:31:01 PM: npm ERR!

6:31:01 PM: npm ERR! Failed at the js-portfolio@1.0.0 build script.

6:31:01 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

6:31:01 PM: npm ERR! A complete log of this run can be found in:

6:31:01 PM: npm ERR! /opt/buildhome/.npm/_logs/2021-07-27T21_31_01_718Z-debug.log

6:31:01 PM: ​

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: “build.command” failed

6:31:01 PM: ────────────────────────────────────────────────────────────────

6:31:01 PM: ​

6:31:01 PM: Error message

6:31:01 PM: Command failed with exit code 1: npm run build

6:31:01 PM: ​

6:31:01 PM: Error location

6:31:01 PM: In build.command from netlify.toml:

6:31:01 PM: npm run build

6:31:01 PM: ​

6:31:01 PM: Resolved config

6:31:01 PM: build:

6:31:01 PM: command: npm run build

6:31:01 PM: commandOrigin: config

6:31:01 PM: publish: /opt/build/repo/dist

6:31:01 PM: publishOrigin: config

6:31:02 PM: Caching artifacts

6:31:02 PM: Started saving node modules

6:31:02 PM: Finished saving node modules

6:31:02 PM: Started saving build plugins

6:31:02 PM: Finished saving build plugins

6:31:02 PM: Started saving pip cache

6:31:02 PM: Finished saving pip cache

6:31:02 PM: Started saving emacs cask dependencies

6:31:02 PM: Finished saving emacs cask dependencies

6:31:02 PM: Started saving maven dependencies

6:31:02 PM: Finished saving maven dependencies

6:31:02 PM: Started saving boot dependencies

6:31:02 PM: Finished saving boot dependencies

6:31:02 PM: Started saving rust rustup cache

6:31:02 PM: Finished saving rust rustup cache

6:31:02 PM: Started saving go dependencies

6:31:02 PM: Finished saving go dependencies

6:31:04 PM: Build failed due to a user error: Build script returned non-zero exit code: 2

6:31:05 PM: Creating deploy upload records

6:31:05 PM: Failing build: Failed to build site

6:31:05 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2

6:31:05 PM: Finished processing build request in 20.056837982s

TENGO ESTE ERROR, ALGUNA SOLUCION?

No hay respuestas
para escribir tu comentario
Curso de Webpack [Empieza Gratis]

Curso de Webpack [Empieza Gratis]

Construye aplicaciones React usando Webpack. Aprende a configurar y optimizar tu entorno de desarrollo con loaders, compresión CSS y análisis de paquetes. Despliega tu proyecto fácilmente en producción y mejora el rendimiento.

Curso de Webpack [Empieza Gratis]
Curso de Webpack [Empieza Gratis]

Curso de Webpack [Empieza Gratis]

Construye aplicaciones React usando Webpack. Aprende a configurar y optimizar tu entorno de desarrollo con loaders, compresión CSS y análisis de paquetes. Despliega tu proyecto fácilmente en producción y mejora el rendimiento.