Skip to content

Vite a (#2287)

Vite a (#2287) #17

Triggered via push November 20, 2024 00:46
Status Failure
Total duration 1m 53s
Artifacts

viteToHeroku.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
build
Error: Command failed: heroku container:push web --app foodoasisvite › Warning: heroku update available from 9.4.0 to 9.5.0. #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 1.35kB done #1 DONE 0.0s #2 [internal] load metadata for docker.io/library/node:lts-bullseye-slim #2 DONE 0.2s #3 [internal] load .dockerignore #3 transferring context: 112B done #3 DONE 0.0s #4 [clientbuilder 1/9] FROM docker.io/library/node:lts-bullseye-slim@sha256:ba5f9086411a1f5b7b8849c033321075d7143312ac3e1547132afd82de78219b #4 DONE 0.0s #5 [internal] load build context #5 transferring context: 32.44kB 0.0s done #5 DONE 0.0s #6 [clientbuilder 4/9] COPY client/package.json . #6 CACHED #7 [clientbuilder 2/9] RUN mkdir /app #7 CACHED #8 [clientbuilder 3/9] WORKDIR /app #8 CACHED #9 [clientbuilder 6/9] RUN npm ci #9 CACHED #10 [clientbuilder 5/9] COPY client/package-lock.json . #10 CACHED #11 [serverbuilder 6/13] COPY ./server/tsconfig.json ./ #11 CACHED #12 [serverbuilder 7/13] COPY ./server/package.json ./ #12 CACHED #13 [serverbuilder 5/13] RUN mkdir build #13 CACHED #14 [stage-2 3/9] COPY ./server/package.json ./ #14 CACHED #15 [serverbuilder 4/13] WORKDIR /usr/src/app #15 CACHED #16 [serverbuilder 8/13] COPY ./server/package-lock.json ./ #16 CACHED #17 [serverbuilder 9/13] COPY ./server/middleware/ ./middleware #17 CACHED #18 [serverbuilder 13/13] RUN npm ci --quiet && npm run build #18 CACHED #19 [stage-2 5/9] RUN npm ci --quiet #19 CACHED #20 [stage-2 6/9] COPY --from=serverBuilder /usr/src/app/build ./ #20 CACHED #21 [serverbuilder 11/13] COPY ./server/app/ ./app #21 CACHED #22 [stage-2 2/9] WORKDIR /fola #22 CACHED #23 [serverbuilder 10/13] COPY ./server/types/ ./types #23 CACHED #24 [serverbuilder 12/13] COPY ./server/server.ts ./ #24 CACHED #25 [stage-2 4/9] COPY ./server/package-lock.json ./ #25 CACHED #26 [serverbuilder 2/13] WORKDIR /usr/src #26 CACHED #27 [serverbuilder 3/13] COPY tsconfig.json ./ #27 CACHED #28 [clientbuilder 7/9] COPY client . #28 CACHED #29 [stage-2 7/9] COPY ./server/uploads ./uploads #29 CACHED #30 [clientbuilder 8/9] RUN npm run build #30 0.268 #30 0.268 > [email protected] build #30 0.268 > tsc && vite build #30 0.268 #30 9.426 setupTests.ts(1,1): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig. #30 9.426 setupTests.ts(2,1): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig. #30 ERROR: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2 ------ > [clientbuilder 8/9] RUN npm run build: 0.268 0.268 > [email protected] build 0.268 > tsc && vite build 0.268 9.426 setupTests.ts(1,1): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig. 9.426 setupTests.ts(2,1): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig. ------ Dockerfile:12 -------------------- 10 | COPY client . 11 | ENV NODE_ENV "production" 12 | >>> RUN npm run build 13 | RUN echo package.json 14 | -------------------- ERROR: failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 2 › Error: docker build exited with Error: 1
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, akhileshns/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/