cloudflare-pages[bot]
commented
10 months ago Deploying with 
Cloudflare Pages
| Latest commit: |
ee2dcd1
|
| Status: | ā Deploy successful! |
| Preview URL: | https://988114cc.tilfeldigeord-no.pages.dev |
| Branch Preview URL: | https://bump-11ty.tilfeldigeord-no.pages.dev |
Okay, so this had bugged me for a while, but not enough to actually fix it š Until now.
I noticed that deployment of #58 didn't work, and I just assumed it was related to my Eleventy config not working (major update, and all), but never bothered to look into it. Then I did, and saw that everything worked fine locally, but deployment to Netlify failed. Then, looking at the deploy logs:
Huh. I don't remember ever setting the Node version anywhere.
Some more digging, and I eventually found this explanation.
IIUC, Netlify defaults to the current LTS Node version on first deploy, unless specified otherwise. This was probably something like v13 at the time of first deploy (June-ish 2020), and was never changed. Which explains the error.
So, I tried this, to specify v18 (current LTS) of Node:
...and it worked!
So, for now, I'm happy (again) with the Netlify setup, so I've removed the CloudFlare Pages experiment, and will be closing #67 as well.
Netlify should also work well for hosting a function/API (#24), so that's nice, I guess.
The only thing that would be simpler with CloudFlare Pages, is free analytics, which would solve #70, but I'll just leave that open for now.
Referenced issues
Closes #62 Closes #67