search

Azure / static-web-apps

Azure Static Web Apps. For bugs and feature requests, please create an issue in this repo. For community discussions, latest updates, kindly refer to the Discussions Tab. To know what's new in Static Web Apps, visit https://aka.ms/swa/ThisMonth
https://aka.ms/swa
MIT License
324 stars 56 forks source link

error Gatsby requires Node.js 18.0.0 or higher (you have v16.18.0) #994

Closed Draey closed 1 year ago

Draey commented 1 year ago

Hi, I'm quite new to the development space, and when trying to deploy the first iteration of my gatsby blog app, the app won't complete and returns these errors when attempting to deploy and build the app.

The end of the error it states that my node js is old, which is not true, as the host that I'm doing the development on is actually running v18.9.0.

`Run Azure/static-web-apps-deploy@v1 2 with: 3 azure_static_web_apps_api_token: 4 repo_token: 5 action: upload 6 app_location: / 7 output_location: public 8 /usr/bin/docker run --name b1cce6bde446b9be4178adc499235d_9e2cdd --label 290506 --workdir /github/workspace --rm -e "INPUT_AZURE_STATIC_WEB_APPS_API_TOKEN" -e "INPUT_REPO_TOKEN" -e "INPUT_ACTION" -e "INPUT_APP_LOCATION" -e "INPUT_API_LOCATION" -e "INPUT_OUTPUT_LOCATION" -e "INPUT_API_BUILD_COMMAND" -e "INPUT_APP_ARTIFACT_LOCATION" -e "INPUT_APP_BUILD_COMMAND" -e "INPUT_ROUTES_LOCATION" -e "INPUT_SKIP_APP_BUILD" -e "INPUT_CONFIG_FILE_LOCATION" -e "INPUT_SKIP_API_BUILD" -e "INPUT_PRODUCTION_BRANCH" -e "INPUT_DEPLOYMENT_ENVIRONMENT" -e "INPUT_IS_STATIC_EXPORT" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/gatsby-starter-blog/gatsby-starter-blog":"/github/workspace" 290506:66b1cce6bde446b9be4178adc499235d 9 DeploymentId: 3889d358-3d60-4ec0-a385-99277431e1c3 10

11 App Directory Location: '/' was found. 12 Looking for event info 13 Starting to build app with Oryx 14 Azure Static Web Apps utilizes Oryx to build both static applications and Azure Functions. You can find more details on Oryx here: https://github.com/microsoft/Oryx 15 ---Oryx build logs--- 16

17

18 Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx 19 You can report issues at https://github.com/Microsoft/Oryx/issues 20

21 Oryx Version: 0.2.20221103.1, Commit: a2c65dde152b749fea395f4d1242ea9350942258, ReleaseTagName: 20221103.1 22

23 Build Operation ID: |QLuZ9S+YQbQ=.a75c22ee_ 24 Repository Commit : 70a1c310b247346976637ad299c6ad4ac6449ab0 25

26 Detecting platforms... 27 Detected following platforms: 28 nodejs: 16.18.0 29 Version '16.18.0' of platform 'nodejs' is not installed. Generating script to install it... 30 Detected the following frameworks: Gatsby 31

32

33 Source directory : /github/workspace 34 Destination directory: /bin/staticsites/ss-oryx/app 35

36

37 Downloading and extracting 'nodejs' version '16.18.0' to '/opt/nodejs/16.18.0'... 38 Detected image debian flavor: bullseye. 39 Downloaded in 0 sec(s). 40 Verifying checksum... 41 Extracting contents... 42 performing sha512 checksum for: nodejs... 43 Done in 1 sec(s). 44

45 Removing existing manifest file 46 Creating directory for command manifest file if it does not exist 47 Creating a manifest file... 48 Node Build Command Manifest file created. 49

50 Using Node version: 51 v16.18.0 52

53 Using Npm version: 54 8.19.2 55

56 Running 'npm install --unsafe-perm'... 57

58 npm WARN ERESOLVE overriding peer dependency 59 npm WARN While resolving: express-graphql@0.12.0 60 npm WARN Found: graphql@16.6.0 61 npm WARN node_modules/graphql 62 npm WARN peer graphql@"*" from @ardatan/relay-compiler@12.0.0 63 npm WARN node_modules/@ardatan/relay-compiler 64 npm WARN @ardatan/relay-compiler@"12.0.0" from @graphql-tools/relay-operation-optimizer@6.5.10 65 npm WARN node_modules/@graphql-tools/relay-operation-optimizer 66 npm WARN 28 more (@graphql-codegen/add, @graphql-codegen/core, ...) 67 npm WARN 68 npm WARN Could not resolve dependency: 69 npm WARN peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0 70 npm WARN node_modules/express-graphql 71 npm WARN express-graphql@"^0.12.0" from gatsby@5.0.0 72 npm WARN node_modules/gatsby 73 npm WARN 74 npm WARN Conflicting peer dependency: graphql@15.8.0 75 npm WARN node_modules/graphql 76 npm WARN peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0 77 npm WARN node_modules/express-graphql 78 npm WARN express-graphql@"^0.12.0" from gatsby@5.0.0 79 npm WARN node_modules/gatsby 80 npm WARN ERESOLVE overriding peer dependency 81 npm WARN While resolving: react-server-dom-webpack@0.0.0-experimental-c8b778b7f-20220825 82 npm WARN Found: react@18.2.0 83 npm WARN node_modules/react 84 npm WARN react@"^18.1.0" from the root project 85 npm WARN 8 more (@gatsbyjs/reach-router, gatsby, gatsby-link, ...) 86 npm WARN 87 npm WARN Could not resolve dependency: 88 npm WARN peer react@"0.0.0-experimental-c8b778b7f-20220825" from react-server-dom-webpack@0.0.0-experimental-c8b778b7f-20220825 89 npm WARN node_modules/react-server-dom-webpack 90 npm WARN react-server-dom-webpack@"0.0.0-experimental-c8b778b7f-20220825" from gatsby@5.0.0 91 npm WARN node_modules/gatsby 92 npm WARN 93 npm WARN Conflicting peer dependency: react@0.0.0-experimental-c8b778b7f-20220825 94 npm WARN node_modules/react 95 npm WARN peer react@"0.0.0-experimental-c8b778b7f-20220825" from react-server-dom-webpack@0.0.0-experimental-c8b778b7f-20220825 96 npm WARN node_modules/react-server-dom-webpack 97 npm WARN react-server-dom-webpack@"0.0.0-experimental-c8b778b7f-20220825" from gatsby@5.0.0 98 npm WARN node_modules/gatsby 99 npm WARN EBADENGINE Unsupported engine { 100 npm WARN EBADENGINE package: '@gatsbyjs/parcel-namer-relative-to-cwd@2.0.0', 101 npm WARN EBADENGINE required: { node: '>=18.0.0', parcel: '2.x' }, 102 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 103 npm WARN EBADENGINE } 104 npm WARN EBADENGINE Unsupported engine { 105 npm WARN EBADENGINE package: 'babel-plugin-remove-graphql-queries@5.0.0', 106 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 107 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 108 npm WARN EBADENGINE } 109 npm WARN EBADENGINE Unsupported engine { 110 npm WARN EBADENGINE package: 'babel-preset-gatsby@3.0.0', 111 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 112 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 113 npm WARN EBADENGINE } 114 npm WARN EBADENGINE Unsupported engine { 115 npm WARN EBADENGINE package: 'gatsby@5.0.0', 116 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 117 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 118 npm WARN EBADENGINE } 119 npm WARN EBADENGINE Unsupported engine { 120 npm WARN EBADENGINE package: 'gatsby-cli@5.0.0', 121 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 122 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 123 npm WARN EBADENGINE } 124 npm WARN EBADENGINE Unsupported engine { 125 npm WARN EBADENGINE package: 'gatsby-core-utils@4.0.0', 126 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 127 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 128 npm WARN EBADENGINE } 129 npm WARN EBADENGINE Unsupported engine { 130 npm WARN EBADENGINE package: 'gatsby-graphiql-explorer@3.0.0', 131 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 132 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 133 npm WARN EBADENGINE } 134 npm WARN EBADENGINE Unsupported engine { 135 npm WARN EBADENGINE package: 'gatsby-link@5.0.0', 136 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 137 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 138 npm WARN EBADENGINE } 139 npm WARN EBADENGINE Unsupported engine { 140 npm WARN EBADENGINE package: 'gatsby-page-utils@3.0.0', 141 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 142 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 143 npm WARN EBADENGINE } 144 npm WARN EBADENGINE Unsupported engine { 145 npm WARN EBADENGINE package: 'gatsby-plugin-feed@5.0.0', 146 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 147 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 148 npm WARN EBADENGINE } 149 npm WARN EBADENGINE Unsupported engine { 150 npm WARN EBADENGINE package: 'gatsby-plugin-manifest@5.0.0', 151 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 152 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 153 npm WARN EBADENGINE } 154 npm WARN EBADENGINE Unsupported engine { 155 npm WARN EBADENGINE package: 'gatsby-plugin-page-creator@5.0.0', 156 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 157 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 158 npm WARN EBADENGINE } 159 npm WARN EBADENGINE Unsupported engine { 160 npm WARN EBADENGINE package: 'gatsby-plugin-sharp@5.0.0', 161 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 162 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 163 npm WARN EBADENGINE } 164 npm WARN EBADENGINE Unsupported engine { 165 npm WARN EBADENGINE package: 'gatsby-plugin-typescript@5.0.0', 166 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 167 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 168 npm WARN EBADENGINE } 169 npm WARN EBADENGINE Unsupported engine { 170 npm WARN EBADENGINE package: 'gatsby-plugin-utils@4.0.0', 171 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 172 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 173 npm WARN EBADENGINE } 174 npm WARN EBADENGINE Unsupported engine { 175 npm WARN EBADENGINE package: 'gatsby-react-router-scroll@6.0.0', 176 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 177 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 178 npm WARN EBADENGINE } 179 npm WARN EBADENGINE Unsupported engine { 180 npm WARN EBADENGINE package: 'gatsby-remark-images@7.0.0', 181 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 182 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 183 npm WARN EBADENGINE } 184 npm WARN EBADENGINE Unsupported engine { 185 npm WARN EBADENGINE package: 'gatsby-remark-prismjs@7.0.0', 186 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 187 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 188 npm WARN EBADENGINE } 189 npm WARN EBADENGINE Unsupported engine { 190 npm WARN EBADENGINE package: 'gatsby-remark-responsive-iframe@6.0.0', 191 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 192 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 193 npm WARN EBADENGINE } 194 npm WARN EBADENGINE Unsupported engine { 195 npm WARN EBADENGINE package: 'gatsby-script@2.0.0', 196 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 197 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 198 npm WARN EBADENGINE } 199 npm WARN EBADENGINE Unsupported engine { 200 npm WARN EBADENGINE package: 'gatsby-sharp@1.0.0', 201 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 202 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 203 npm WARN EBADENGINE } 204 npm WARN EBADENGINE Unsupported engine { 205 npm WARN EBADENGINE package: 'gatsby-source-filesystem@5.0.0', 206 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 207 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 208 npm WARN EBADENGINE } 209 npm WARN EBADENGINE Unsupported engine { 210 npm WARN EBADENGINE package: 'gatsby-telemetry@4.0.0', 211 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 212 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 213 npm WARN EBADENGINE } 214 npm WARN EBADENGINE Unsupported engine { 215 npm WARN EBADENGINE package: 'gatsby-transformer-remark@6.0.0', 216 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 217 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 218 npm WARN EBADENGINE } 219 npm WARN EBADENGINE Unsupported engine { 220 npm WARN EBADENGINE package: 'gatsby-transformer-sharp@5.0.0', 221 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 222 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 223 npm WARN EBADENGINE } 224 npm WARN EBADENGINE Unsupported engine { 225 npm WARN EBADENGINE package: 'gatsby-worker@2.0.0', 226 npm WARN EBADENGINE required: { node: '>=18.0.0' }, 227 npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' } 228 npm WARN EBADENGINE } 229 npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility 230 npm WARN deprecated async-cache@1.1.0: No longer maintained. Use lru-cache version 7.6 or higher, and provide an asynchronous fetchMethod option. 231 npm WARN deprecated @types/keyv@4.2.0: This is a stub types definition. keyv provides its own type definitions, so you do not need this installed. 232 npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained 233 npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained 234 npm WARN deprecated @hapi/address@2.1.4: Moved to 'npm install @sideway/address' 235 npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained 236 npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. 237 npm WARN deprecated @hapi/joi@15.1.1: Switch to 'npm install joi' 238

239 added 1476 packages, and audited 1477 packages in 1m 240

241 302 packages are looking for funding 242 run npm fund for details 243

244 found 0 vulnerabilities 245

246 Running 'npm run build'... 247

248

249

gatsby-starter-blog@0.1.0 build 250 gatsby build 251

252 error Gatsby requires Node.js 18.0.0 or higher (you have v16.18.0). 253 Upgrade Node to the latest stable release: https://gatsby.dev/upgrading-node-js 254

255

256 ---End of Oryx build logs--- 257 Oryx has failed to build the solution. 258

259 For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ 260 If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ 261 Exiting`

Apologies if this issue has been mentioned before, I couldn't find it in the issues section of your github.

vivekjilla commented 1 year ago

Hi @Draey, can you try specifying the node version as 18 in your package.json, using the engines property

{
  "name": "...",
  "version": "...",
  ...
  "engines": {
    "node": "18.x"
  }
}
Draey commented 1 year ago

Hi, thank you very much for the response. That resolved it, but I now get the following error :(

Oryx has failed to build the solution.

Running 'npm install --unsafe-perm'...
[57](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:58)

[58](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:59)
npm ERR! code ERESOLVE
[59](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:60)
npm ERR! ERESOLVE could not resolve
[60](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:61)
npm ERR! 
[61](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:62)
npm ERR! While resolving: gatsby-plugin-feed@5.0.0
[62](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:63)
npm ERR! Found: gatsby@5.2.0-next.0
[63](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:64)
npm ERR! node_modules/gatsby
[64](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:65)
npm ERR!   gatsby@"^5.2.0-next.0" from the root project
[65](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:66)
npm ERR! 
[66](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:67)
npm ERR! Could not resolve dependency:
[67](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:68)
npm ERR! peer gatsby@"^5.0.0-next" from gatsby-plugin-feed@5.0.0
[68](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:69)
npm ERR! node_modules/gatsby-plugin-feed
[69](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:70)
npm ERR!   gatsby-plugin-feed@"^5.0.0" from the root project
[70](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:71)
npm ERR! 
[71](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:72)
npm ERR! Conflicting peer dependency: gatsby@5.0.1
[72](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:73)
npm ERR! node_modules/gatsby
[73](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:74)
npm ERR!   peer gatsby@"^5.0.0-next" from gatsby-plugin-feed@5.0.0
[74](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:75)
npm ERR!   node_modules/gatsby-plugin-feed
[75](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:76)
npm ERR!     gatsby-plugin-feed@"^5.0.0" from the root project
[76](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:77)
npm ERR! 
[77](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:78)
npm ERR! Fix the upstream dependency conflict, or retry
[78](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:79)
npm ERR! this command with --force, or --legacy-peer-deps
[79](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:80)
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
[80](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:81)
npm ERR! 
[81](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:82)
npm ERR! See /github/home/.npm/eresolve-report.txt for a full report.
[82](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:83)

[83](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:84)
npm ERR! A complete log of this run can be found in:
[84](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:85)
npm ERR!     /github/home/.npm/_logs/2022-11-21T11_44_32_775Z-debug-0.log
[85](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:86)

[86](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:87)

[87](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:88)
---End of Oryx build logs---
[88](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:89)
Oryx has failed to build the solution.
[89](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:90)

[90](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:91)
For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
[91](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:92)
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
[92](https://github.com/Draey/gatsby-starter-blog/actions/runs/3514042100/jobs/5887696348#step:4:93)
Exiting
vivekjilla commented 1 year ago

From the error, it looks like there are conflicting peer dependencies in your package.json. See if you can resolve those conflicts locally. Otherwise, one workaround is to set --legacy-peer-deps flag or --flag using environment variables in your workflow.yml. Reference: https://github.com/Azure/static-web-apps/issues/989

sulabh-msft commented 1 year ago

@Draey Please let us know if you were able to resolve the issue.

sulabh-msft commented 1 year ago

Closing the issue. Please feel re-open the issue in case you are still hitting the same issue.

tausiq2003 commented 1 year ago

@sulabh-msft I have added this to package-lock.json file as mentioned above "engines":{"node": "18.x" ... but still its not working

added 1486 packages, and audited 1487 packages in 1m

315 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Running 'npm run build'...

> gatsby-starter-blog@0.1.0 build
> gatsby build

error Gatsby requires Node.js 18.0.0 or higher (you have v16.19.0).
Upgrade Node to the latest stable release: https://gatsby.dev/upgrading-node-js

---End of Oryx build logs---
Oryx has failed to build the solution.
gabschlemper commented 1 year ago

Same error for me.. I've been trying a lot of things and still not working. So I just change the deployment server.

tausiq2003 commented 1 year ago

Same error for me.. I've been trying a lot of things and still not working. So I just change the deployment server.

change server means region?

gabschlemper commented 1 year ago

No, i'm just using Vercel instead Netlify and it was really faster and easy. (https://vercel.com)