Deployment Failed... Why?
Hi all
I just deployed a site with CF Pages and it failed, I've never had that happen before and I don't see an option to view how it failed.
This answer: https://community.cloudflare.com/t/deployment-of-fails-with-no-log/578381/4 mentions the CF team might be able to help
Thanks for your time
29 Replies
what's the deployment id? we can help but not with nothing to lookup :p
8248643e-425b-4a31-8dfe-6664faae2b34
We got an internal error, that's fun - if you try again does it work?
i'll give it a go now, one sec
0a0cea1b-3f0d-4e0c-af0a-36d49df1069e
no luck :/
it fails immediately
i'm using direct file upload
and specifying a
_routes.json file which is experimental_routes.json isn't experimental but let me look hmm
oh, when I upload files I get this
oh haha, that was from when we first added
So from the error, it seems like you may have an bad import path in the Worker/Function
oh, it's a sveltekit project so the imports should have been resolved when it was built but I'll have a manual look, thanks for responding!
Yeah, it seems like it's trying to go up a directory, like you may have a
import ... from '../<blah>' and that is what is failing (there is no higher dir)@Walshy | Workers/Pages I decided to try git integration for funsies and got this:
needs a higher node, you can do an env var:
NODE_VERSION value 22 to use latest node 22👍 is there a reason the build process uses node
18.17 by default if it's unsupported?sadly because Pages is essentially abandoned and no longer getting updates. It works, but updates are very unlikely. I'd recommend you pin the version you want such as
22.14.0, as even 22 or 20 will be old versions of 22 and 20 respectively, with security issues.oh, that's unfortunate to hear. what's the alternative? workers or wait for the new merged platform to release?
Workers Assets + Workers CI is the effective successor, but technically still beta, so your mileage may vary there too for now.
:/ anyhow thanks for the help
hmm, this didn't seem to work both with values of
22 and 22.12.0
in both instances the build logs output npm ERR! notsup Actual: {"npm":"9.6.7","node":"v18.17.1"}did you add it to both your production and preview environment configs?
you could also add a
.node-version file to the repo if that's easier
didn't manage to get that to work (see above image) 🤔 also the .node-version didn't play nice
i got this line in the log:
perhaps I'm not setting them correctly
although I double checked, their set for both production and preview modes
and the log seems to think they're their as well
that sounds like workers ci
are you in workers ci not pages ci? :thonk:
definitely a pages project, with the node env var set to 22 and a .node-version file with 22 in, here's a snippet from the latest build log (28beba6d-f1ed-466b-8580-21a50b461ba7):
Oh you're using wrangler.toml
Right...
is that bad? 😳
Wrangler.toml becomes the source of truth
So setting this in the dash doesn't do any change
ahhh, i need to specify node version there then?
You need to set it in wrangler.toml
🤦♂️ thank you
i'll try again
There should be a warning in the dash settings saying this
But I'm not sure if that got removed during the settings revamped
I didn't see anything mentioning it