Why am I having conflicts with my dependency tree?
rick002
HOBBYOP

2 years ago

[Region: us-west1]

==============

Using Nixpacks

==============

context: 894a2a2e85b3541af1b7808826006403

╔════════ Nixpacks v1.21.2 ═══════╗

║ setup │ nodejs18, npm-9x ║

║─────────────────────────────────║

║ install │ npm ci ║

║─────────────────────────────────║

║ build │ npm run build:ssr ║

║─────────────────────────────────║

║ start │ npm start ║

╚═════════════════════════════════╝

0 building with "default" instance using docker driver

1 [internal] load build definition from Dockerfile

1 transferring dockerfile: 2.13kB done

1 DONE 0.0s

2 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1707782610

2 DONE 0.1s

3 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1707782610@sha256:8f4b0fd95dc3311cf9a59f236d8d7d7f956fe21a2a1d64b53c82f12c4e859f09

3 DONE 0.0s

4 [internal] load .dockerignore

4 transferring context: 2B done

4 DONE 0.0s

5 [internal] load build context

5 transferring context: 15.00MB 0.1s done

5 DONE 0.1s

6 [stage-0 2/10] WORKDIR /app/

6 CACHED

7 [stage-0 3/10] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix

7 CACHED

8 [stage-0 4/10] RUN nix-env -if .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix && nix-collect-garbage -d

8 CACHED

9 [stage-0 5/10] COPY . /app/.

9 DONE 0.1s

18 Replies

2 years ago

I'm not seeing any issues there, please use this https://bookmarklets.up.railway.app/log-downloader/

attach the logs you got from that.


rick002
HOBBYOP

2 years ago

Sorry, it's not clear for me how to use it


2 years ago

follow the 3 steps listed on that page.


rick002
HOBBYOP

2 years ago

Finally did it

Attachments


rick002
HOBBYOP

2 years ago

It is running perfectly in local tho.


2 years ago

if you deleted your local node_modules folder and ran npm install would you get these same errors?


rick002
HOBBYOP

2 years ago

Not at all.


2 years ago

have you just confirmed that?


rick002
HOBBYOP

2 years ago

Sure


2 years ago

sure?


rick002
HOBBYOP

2 years ago

I even tried to include an "install": "npm install --legacy-peer-deps" script


2 years ago

if you deleted your local node_modules folder and ran npm install would you get these same errors?

have you done this? (Y/N)


rick002
HOBBYOP

2 years ago

Yes


rick002
HOBBYOP

2 years ago

I would like to configure the docker build stage in railway to run npm install --legacy-peer-deps instead.

Is it possible?


2 years ago

do you need to run that locally for you to not receive errors?


rick002
HOBBYOP

2 years ago

No, locally I just run npm install and everything works fine.


2 years ago

what version of node are you using locally?


rick002
HOBBYOP

2 years ago

Locally, I am using nvm to activate node 18.


Loading...