Builds are failing (npmjs unreachable?)
Hello, my Next app's builds started to fail today at
npm ci seemingly because it can't make contact with the npmjs registry to install packages that exist on npmjs.com. I tried removing one, re-build, then it failed again citing the same reason but a different package.
I tried regenerating the package-lock and rebuilding, didn't work. Tried running npm ci locally and that works fine.
Anyone know what's happening here / what to do?
12 Replies
Project ID:
N/A72baa825-3b05-4111-be4d-73d2953d4523
what version of node is railway using and what version of node are you using locally?
How do I check what version of node Railway is using? I'm using 18.0 locally and the Dockerfile in the repo is using node:18-alpine.
oh then if railway is building with your dockerfile its using the image you specified in the dockerfile
can you build and run the dockerfile locally?
It built and ran fine on local docker
Struggling to think of what else could be causing
i have no idea either, ill pull in a team member monday for you
Thanks @Brody
Flagging this thread. A team member will be with you shortly.
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Hi Angelo. It started working the next day. Thank you for taking a look. If it was a rate limit, it would be helpful to get an error message about that and what/how to upgrade the plan to get around.
Angelo is talking about a rate limit imposed onto railway from the npm package repository, nothing to do with what plan you have, and not your fault at all