Deployment Failed... Why?

Evorage · 2025-03-12T17:29:15.697Z

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

W

Walshy•3/12/25, 8:07 PM

what's the deployment id? we can help but not with nothing to lookup :p

WWalshy what's the deployment id? we can help but not with nothing to lookup :p

E

EvorageOP•3/12/25, 9:26 PM

8248643e-425b-4a31-8dfe-6664faae2b34

W

Walshy•3/12/25, 9:27 PM

We got an internal error, that's fun - if you try again does it work?

E

EvorageOP•3/12/25, 9:27 PM

i'll give it a go now, one sec

E

EvorageOP•3/12/25, 9:28 PM

0a0cea1b-3f0d-4e0c-af0a-36d49df1069e
no luck :/

E

EvorageOP•3/12/25, 9:28 PM

it fails immediately

E

EvorageOP•3/12/25, 9:29 PM

i'm using direct file upload

E

EvorageOP•3/12/25, 9:30 PM

and specifying a

_routes.json

_routes.json

file which is experimental

W

Walshy•3/12/25, 9:42 PM

_routes.json isn't experimental but let me look hmm

E

EvorageOP•3/12/25, 9:44 PM

oh, when I upload files I get this

W

Walshy•3/12/25, 9:45 PM

oh haha, that was from when we first added

W

Walshy•3/12/25, 9:45 PM

So from the error, it seems like you may have an bad import path in the Worker/Function

E

EvorageOP•3/12/25, 9:46 PM

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!

W

Walshy•3/12/25, 9:47 PM

Yeah, it seems like it's trying to go up a directory, like you may have a

import ... from '../<blah>'

import ... from '../<blah>'

and that is what is failing (there is no higher dir)

E

EvorageOP•3/12/25, 10:26 PM

@Walshy | Workers/Pages I decided to try git integration for funsies and got this:

22:18:47.057    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
22:18:47.058    Installing project dependencies: npm clean-install --progress=false
22:18:48.405    npm ERR! code EBADENGINE
22:18:48.406    npm ERR! engine Unsupported engine
22:18:48.406    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.406    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.407    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
22:18:48.407    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
22:18:48.408    
22:18:48.408    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-12T22_18_47_771Z-debug-0.log

22:18:47.057    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
22:18:47.058    Installing project dependencies: npm clean-install --progress=false
22:18:48.405    npm ERR! code EBADENGINE
22:18:48.406    npm ERR! engine Unsupported engine
22:18:48.406    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.406    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.407    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
22:18:48.407    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
22:18:48.408    
22:18:48.408    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-12T22_18_47_771Z-debug-0.log

22:18:47.057    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
22:18:47.058    Installing project dependencies: npm clean-install --progress=false
22:18:48.405    npm ERR! code EBADENGINE
22:18:48.406    npm ERR! engine Unsupported engine
22:18:48.406    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.406    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.407    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
22:18:48.407    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
22:18:48.408    
22:18:48.408    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-12T22_18_47_771Z-debug-0.log

22:18:47.057    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
22:18:47.058    Installing project dependencies: npm clean-install --progress=false
22:18:48.405    npm ERR! code EBADENGINE
22:18:48.406    npm ERR! engine Unsupported engine
22:18:48.406    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.406    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
22:18:48.407    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
22:18:48.407    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
22:18:48.408    
22:18:48.408    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-12T22_18_47_771Z-debug-0.log

W

Walshy•3/12/25, 10:29 PM

needs a higher node, you can do an env var:

NODE_VERSION

NODE_VERSION

value

to use latest node 22

E

EvorageOP•3/12/25, 10:30 PM

is there a reason the build process uses node

18.17

18.17

by default if it's unsupported?

EEvorage 👍 is there a reason the build process uses node `18.17` by default if it's unsu...

J

James•3/12/25, 10:36 PM

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

22.14.0

, as even

or

will be old versions of

and

respectively, with security issues.

JJames sadly because Pages is essentially abandoned and no longer getting updates. It w...

E

EvorageOP•3/12/25, 10:37 PM

oh, that's unfortunate to hear. what's the alternative? workers or wait for the new merged platform to release?

EEvorage oh, that's unfortunate to hear. what's the alternative? workers or wait for the ...

J

James•3/12/25, 10:38 PM

Workers Assets + Workers CI is the effective successor, but technically still beta, so your mileage may vary there too for now.

E

EvorageOP•3/12/25, 10:39 PM

:/ anyhow thanks for the help

WWalshy needs a higher node, you can do an env var: `NODE_VERSION` value `22` to use lat...

E

EvorageOP•3/12/25, 10:47 PM

hmm, this didn't seem to work both with values of

and

22.12.0

22.12.0

in both instances the build logs output

npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}

npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}

J

James•3/12/25, 10:50 PM

did you add it to both your production and preview environment configs?

J

James•3/12/25, 10:50 PM

you could also add a

.node-version

.node-version

file to the repo if that's easier

E

EvorageOP•3/12/25, 10:53 PM

WWalshy needs a higher node, you can do an env var: `NODE_VERSION` value `22` to use lat...

E

EvorageOP•3/13/25, 12:54 AM

didn't manage to get that to work (see above image)

also the .node-version didn't play nice

E

EvorageOP•3/13/25, 12:54 AM

i got this line in the log:

Build environment variables: (none found)

Build environment variables: (none found)

perhaps I'm not setting them correctly

E

EvorageOP•3/13/25, 12:55 AM

although I double checked, their set for both production and preview modes

EEvorage Empty message

E

EvorageOP•3/13/25, 12:55 AM

and the log seems to think they're their as well

EEvorage i got this line in the log: ``` Build environment variables: (none found) ``` pe...

W

Walshy•3/13/25, 12:57 AM

that sounds like workers ci

W

Walshy•3/13/25, 12:57 AM

are you in workers ci not pages ci? :thonk:

E

EvorageOP•3/13/25, 12:59 AM

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):

00:53:27.968    Found wrangler.toml file. Reading build configuration...
00:53:27.976    pages_build_output_dir: .svelte-kit/cloudflare
00:53:27.976    Build environment variables: (none found)
00:53:29.081    Successfully read wrangler.toml file.
00:53:29.144    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
00:53:29.145    Installing project dependencies: npm clean-install --progress=false
00:53:30.355    npm ERR! code EBADENGINE
00:53:30.356    npm ERR! engine Unsupported engine
00:53:30.356    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.356    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.357    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
00:53:30.357    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
00:53:30.358    
00:53:30.358    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-13T00_53_29_798Z-debug-0.log

00:53:27.968    Found wrangler.toml file. Reading build configuration...
00:53:27.976    pages_build_output_dir: .svelte-kit/cloudflare
00:53:27.976    Build environment variables: (none found)
00:53:29.081    Successfully read wrangler.toml file.
00:53:29.144    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
00:53:29.145    Installing project dependencies: npm clean-install --progress=false
00:53:30.355    npm ERR! code EBADENGINE
00:53:30.356    npm ERR! engine Unsupported engine
00:53:30.356    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.356    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.357    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
00:53:30.357    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
00:53:30.358    
00:53:30.358    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-13T00_53_29_798Z-debug-0.log

00:53:27.968    Found wrangler.toml file. Reading build configuration...
00:53:27.976    pages_build_output_dir: .svelte-kit/cloudflare
00:53:27.976    Build environment variables: (none found)
00:53:29.081    Successfully read wrangler.toml file.
00:53:29.144    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
00:53:29.145    Installing project dependencies: npm clean-install --progress=false
00:53:30.355    npm ERR! code EBADENGINE
00:53:30.356    npm ERR! engine Unsupported engine
00:53:30.356    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.356    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.357    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
00:53:30.357    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
00:53:30.358    
00:53:30.358    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-13T00_53_29_798Z-debug-0.log

00:53:27.968    Found wrangler.toml file. Reading build configuration...
00:53:27.976    pages_build_output_dir: .svelte-kit/cloudflare
00:53:27.976    Build environment variables: (none found)
00:53:29.081    Successfully read wrangler.toml file.
00:53:29.144    Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
00:53:29.145    Installing project dependencies: npm clean-install --progress=false
00:53:30.355    npm ERR! code EBADENGINE
00:53:30.356    npm ERR! engine Unsupported engine
00:53:30.356    npm ERR! engine Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.356    npm ERR! notsup Not compatible with your version of node/npm: @eslint/compat@1.2.7
00:53:30.357    npm ERR! notsup Required: {"node":"^18.18.0 || ^20.9.0 || >=21.1.0"}
00:53:30.357    npm ERR! notsup Actual:   {"npm":"9.6.7","node":"v18.17.1"}
00:53:30.358    
00:53:30.358    npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-03-13T00_53_29_798Z-debug-0.log

W

Walshy•3/13/25, 1:01 AM

Oh you're using wrangler.toml

W

Walshy•3/13/25, 1:01 AM

Right...

E

EvorageOP•3/13/25, 1:01 AM

is that bad?

W

Walshy•3/13/25, 1:01 AM

Wrangler.toml becomes the source of truth

W

Walshy•3/13/25, 1:01 AM

So setting this in the dash doesn't do any change

E

EvorageOP•3/13/25, 1:01 AM

ahhh, i need to specify node version there then?

W

Walshy•3/13/25, 1:01 AM

You need to set it in wrangler.toml

E

EvorageOP•3/13/25, 1:01 AM

thank you

E

EvorageOP•3/13/25, 1:02 AM

i'll try again

W

Walshy•3/13/25, 1:02 AM

There should be a warning in the dash settings saying this

W

Walshy•3/13/25, 1:02 AM

But I'm not sure if that got removed during the settings revamped

E

EvorageOP•3/13/25, 1:02 AM

I didn't see anything mentioning it

Similar Threads

Similar Threads

Similar Threads