Node not downloading in pages builds
For the past couple of days many deployments get stuck in the "Downloading node" stage.
Anything I can do to remedy this?
Anything I can do to remedy this?
MI'm getting this exact same issue, getting stuck at downloading node. I haven't managed to get a single deploy (have tried 6 times) in the last 30 minutes
COn build image v2 correct?
COn both build v1 and v2
CHmmm this was happening yesterday as well. @walshydev @johndotawesome
C(If it helps/you want a quick fix, I believe if you use the latest major for each version in v2 its preinstalled https://discord.com/channels/595317990191398933/1020053805263507577/1116491058872864818. If you don't specify in v2, it defaults to 18, it looks like the nodejs download server is just choking, that download is super slow for me locally as well)
WNode pls
CBut if I change the nvmrc to 18, the v1 image won't work anymore. Is there a way to keep 17 on the v1 image and 18 on the v2? (I have about 50 pages projects that depend on the same code, and don't want to manually change everything right now)
WIt will work
WBut v1 or v2, either way we download from Node's site
I think v2 has some pre installed like Chaika said which will help
I think v2 has some pre installed like Chaika said which will help
WLooks like our preinstalled versions are 20.1.0, 18.16.0, 16.20.0, 14.21.3 and 12.22.12
C
I will change to 18 and see if it runs correctly on the v1 imageWAgain, it'll still try and download form Node's site
WI don't expect anything better. Using one of the preinstalled versions is best (but checking with the team)
CThe node 18 deploy went perfectly!
II'm still getting this, btw.
IIt has happened already last week, v2 image, but it's more generalized.
IAnd now it works again.
CRIP nodejs servers
Cdon't forget, there is no nodejs "servers", there is just a single nodejs "server" that wouldn't survive without cache, more details https://nodejs.org/en/blog/announcements/node-js-march-17-incident
Fun things, not to derail this too much. Guessing a combination of the preinstalled versions + nodejs 18/higher versions being more popular and thus being in cache for them helps things
Fun things, not to derail this too much. Guessing a combination of the preinstalled versions + nodejs 18/higher versions being more popular and thus being in cache for them helps things
CYeah if it was a single server it would have died a while ago. They should switch to using R2 or something to happen download
Cit's a single origin server (https://discord.com/channels/595317990191398933/812577823599755274/1097963106942058627), but yea protected/cached by CF
COh I forgot about that
II'd personally move the actual Node.js files to a subdomain on R2 
CI already have a worker that caches stuff like maven and python downloads. Time to add nodejs to it
CBut this is now #off-topic
JApologies about this, y'all! We do have pre-installed major versions of node from 12 through 20, but since our tools detected patch version updates to node 18, it tried to install those (instead of using the slightly older pre-installed version). This is getting fixed very soon.
I'd also like to obviate the need to go upstream for any of these versions, but that will be in the
future
I'd also like to obviate the need to go upstream for any of these versions, but that will be in the
future 
SI also had a similar issue with node 17 and although it took ~9 minutes to download, it did eventually work on a nextjs project. A manual download using the link printed was < 5 seconds for me (~42mb)
Looking at the other comments, perhaps I should try moving to node 18 or above.
Looking at the other comments, perhaps I should try moving to node 18 or above.
JIn v2, setting to major versions 12-20 should use a pre-installed version (no downloading necessary)
