0 building with "builder-HqzT" instance using docker-container driver

1 [internal] load build definition from Dockerfile

1 transferring dockerfile: 442B done

1 DONE 0.0s

2 [internal] load metadata for docker.io/library/node:18

2 DONE 0.1s

3 [internal] load .dockerignore

3 transferring context: 2B done

3 DONE 0.0s

4 [1/7] FROM docker.io/library/node:18@sha256:ca07c02d13baf021ff5aadb3b48bcd1fcdd454826266ac313ce858676e8c1548

4 resolve docker.io/library/node:18@sha256:ca07c02d13baf021ff5aadb3b48bcd1fcdd454826266ac313ce858676e8c1548 0.0s done

4 DONE 0.0s

5 [internal] load build context

5 transferring context: 85.65MB 0.6s done

5 DONE 0.6s

6 [2/7] WORKDIR /app

6 CACHED

7 [3/7] COPY package*.json ./

7 DONE 0.1s

8 [4/7] RUN echo "engine-strict=false" > .npmrc

8 DONE 0.1s

9 [5/7] RUN npm install --legacy-peer-deps

9 41.15 npm warn EBADENGINE Unsupported engine {

9 41.15 npm warn EBADENGINE package: 'react-lottie@1.2.4',

9 41.15 npm warn EBADENGINE required: { npm: '^3.0.0' },

9 41.15 npm warn EBADENGINE current: { node: 'v18.20.4', npm: '10.7.0' }

9 41.15 npm warn EBADENGINE }

9 48.63 npm warn deprecated @swc/register@0.1.10: Use @swc-node/register instead

9 48.63 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

9 48.66 npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported

9 49.61 npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead

9 49.72 npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead

9 49.79 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

9 54.29 npm warn deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported

9 56.01 npm warn deprecated three-mesh-bvh@0.7.8: Deprecated due to three.js version incompatibility. Please use v0.8.0, instead.

9 60.38 npm warn deprecated core-js@2.6.12: core-js@<3.23.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. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

9 79.84

9 79.84 added 1476 packages, and audited 1477 packages in 1m

Im having big trouble to upload and host the new version of my website. I have done some big updates (Payload fra v1 to v2 and so on). Mye project builds fine with npm run build, to the errors ceep hunting me here on Railway. I dont know what more I can do to fix this.

I have tried with both dockerfiles and without. Nothing seems to work. I have read a place that It might be a challange getting to deploy with Mac´s M2 ship, but I dont know if that the case here.

View Deploy details

> ⓘ Deployment information is only viewable by project members and Railway employees.

0 Replies