netlify / netlify/cli

Error: Netlify CLI has terminated unexpectedly, during build

Open
#8,121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
TypeScript
Stars
1.9k
Forks
474
Avg merge
23h 30m
Merged PRs (30d)
53

Description

Describe the bug
Please report this problem at https://ntl.fyi/cli-error including the error details below.

Error: Command failed with exit code 1: C:\Program Files\nodejs\node.exe C:\Users\ASUS\AppData\Roaming\npm\node_modules\netlify-cli\dist\utils\telemetry\request.js {"type":"error","data":{"message":"Error while uploading blobs to deploy store","name":"Error","stack":"Error: Error while uploading blobs to deploy store\n    at toError (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/utils/command-helpers.js:146:16)\n    at logAndThrowError (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/utils/command-helpers.js:152:17)\n    at uploadDeployBlobs (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/commands/deploy/deploy.js:367:16)\n    at async runDeploy (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/commands/deploy/deploy.js:451:9)\n    at async prepAndRunDeploy (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/commands/deploy/deploy.js:667:21)\n    at async deployHandler (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/commands/deploy/deploy.js:803:27)\n    at async fireCoreStep (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/core_step.js:11:98)\n    at async tFireStep (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@netlify/build/lib/time/main.js:19:63)\n    at async file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_step.js:65:296\n    at async pReduce.index (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_steps.js:12:362)","severity":"error","user":{"id":"6483f6dca16db51b93b04e91"},"osName":"win32-x64","cliVersion":"23.9.5","nodejsVersion":"v22.20.0"}}
    at makeError (C:\Users\ASUS\AppData\Roaming\npm\node_modules\netlify-cli\node_modules\execa\lib\error.js:60:11)
    at handlePromise (C:\Users\ASUS\AppData\Roaming\npm\node_modules\netlify-cli\node_modules\execa\index.js:118:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async reportError (file:///C:/Users/ASUS/AppData/Roaming/npm/node_modules/netlify-cli/dist/utils/telemetry/report-error.js:47:5)

  System:
    OS: Windows 11 10.0.26200
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
  Binaries:
    Node: 22.20.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (140.0.3485.54)
Steps to reproduce

netlify deploy --build --prod

Configuration

headersOrigin = "inline"
redirects = []

[functions]

[functions."*"]

[[plugins]]
origin = "default"
package = "@netlify/plugin-nextjs"

[plugins.inputs]

[build]
publish = "C:\dev\opponent\opponent_website_fresh_install_test\opponent-static-website\.next"
publishOrigin = "ui"
commandOrigin = "ui"
command = "npm run build"

[build.environment]

[build.processing]

[build.processing.css]

[build.processing.html]

[build.processing.images]

[build.processing.js]

[build.services]

[[headers]]
for = "/_next/static/*"

[headers.values]
Cache-Control = "public, max-age=31536000, immutable"

Environment

System:
OS: Windows 11 10.0.26200
CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
Memory: 20.56 GB / 31.67 GB
Binaries:
Node: 22.20.0 - C:\Program Files\nodejs\node.EXE
npm: 10.9.3 - C:\Program Files\nodejs\npm.CMD

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing netlify deploy --build --prod on the reported Windows and Node.js setup. Trace the deploy flow around dist/commands/deploy/deploy.js and uploadDeployBlobs, then inspect the error and telemetry paths in dist/utils/command-helpers.js and dist/utils/telemetry/request.js; done means identifying and fixing the upload failure with a verified deploy.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.