building pages failed

18:30:12.333 Using v2 root directory strategy
18:30:12.359 Success: Finished cloning repository files
18:30:13.985 Checking for configuration in a wrangler.toml configuration file (BETA)
18:30:13.986
18:30:14.102 No wrangler.toml file found. Continuing.
18:30:14.250 Detected the following tools from environment: [email protected], [email protected]
18:30:14.251 Installing project dependencies: npm clean-install --progress=false
18:30:15.502 npm ERR! code EBADENGINE
18:30:15.503 npm ERR! engine Unsupported engine
18:30:15.503 npm ERR! engine Not compatible with your version of node/npm: [email protected]
18:30:15.503 npm ERR! notsup Not compatible with your version of node/npm: [email protected]
18:30:15.503 npm ERR! notsup Required: {"node":">=18.18.0"}
18:30:15.504 npm ERR! notsup Actual: {"npm":"9.6.7","node":"v18.17.1"}
18:30:15.505
18:30:15.505 npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2024-09-12T16_30_14_959Z-debug-0.log
18:30:15.515 Error: Exit with error code: 1
18:30:15.515 at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
18:30:15.515 at Object.onceWrapper (node:events:652:26)
18:30:15.515 at ChildProcess.emit (node:events:537:28)
18:30:15.515 at ChildProcess._handle.onexit (node:internal/child_process:291:12)
18:30:15.526 Failed: build command exited with code: 1
18:30:16.556 Failed: error occurred while running build command
18:30:12.333 Using v2 root directory strategy
18:30:12.359 Success: Finished cloning repository files
18:30:13.985 Checking for configuration in a wrangler.toml configuration file (BETA)
18:30:13.986
18:30:14.102 No wrangler.toml file found. Continuing.
18:30:14.250 Detected the following tools from environment: [email protected], [email protected]
18:30:14.251 Installing project dependencies: npm clean-install --progress=false
18:30:15.502 npm ERR! code EBADENGINE
18:30:15.503 npm ERR! engine Unsupported engine
18:30:15.503 npm ERR! engine Not compatible with your version of node/npm: [email protected]
18:30:15.503 npm ERR! notsup Not compatible with your version of node/npm: [email protected]
18:30:15.503 npm ERR! notsup Required: {"node":">=18.18.0"}
18:30:15.504 npm ERR! notsup Actual: {"npm":"9.6.7","node":"v18.17.1"}
18:30:15.505
18:30:15.505 npm ERR! A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2024-09-12T16_30_14_959Z-debug-0.log
18:30:15.515 Error: Exit with error code: 1
18:30:15.515 at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
18:30:15.515 at Object.onceWrapper (node:events:652:26)
18:30:15.515 at ChildProcess.emit (node:events:537:28)
18:30:15.515 at ChildProcess._handle.onexit (node:internal/child_process:291:12)
18:30:15.526 Failed: build command exited with code: 1
18:30:16.556 Failed: error occurred while running build command
6 Replies
Walshy
Walshy3mo ago
18:30:15.503 npm ERR! notsup Required: {"node":">=18.18.0"} 18:30:15.504 npm ERR! notsup Actual: {"npm":"9.6.7","node":"v18.17.1"}
You're on Node.js 18.17.1 but 18.18.0+ is needed you'll need to bump your Node.js version - https://developers.cloudflare.com/pages/configuration/language-support-and-tools/#supported-languages-and-tools
Alix
AlixOP3mo ago
when i do node --version in console i see 20.15.0
Walshy
Walshy3mo ago
Local != build environment You can have whatever ver installed locally but that doesn't mean the build system knows what node version to use It attempts to pickup a ver from the common places (package.json, .nvmrc and .node-version) but if you have none of those all it can do is default to a version
Alix
AlixOP3mo ago
so best to do is to add it in package json so it installs that version got it thanks 1 more question @Walshy | Deploying so this site is for a discord bot to have a dashboard, so the backend is python you know how i could use it or is there a docs for? or do i just need to host the bot on vps and talk with each other
Walshy
Walshy3mo ago
bot would need to be on a vps pages is for sites
Alix
AlixOP3mo ago
thanks
Want results from more Discord servers?
Add your server