Error: Netlify CLI has terminated unexpectedly.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- cli
Research direction
Start by reproducing the failure through the netlify dev entry point on Windows 10 with the reported Node and npm versions. Read the stack trace through Node's filesystem watcher and the bundled chokidar handler; done means the CLI no longer terminates unexpectedly when watching the reported PNG path.
Written by the indexing model from the issue text.
Description
Describe the bug
Error: EBUSY: resource busy or locked, watch 'E:\dev\atarfe-digital\dist\Atarfe Digital 1200x630\Atarfe Digital 1200x630 - Claro.png'
at FSWatcher. (node:internal/fs/watchers:323:19)
at watch (node:fs:3062:36)
at createFsWatchInstance (file:///C:/Users//AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:126:16)
at setFsWatchListener (file:///C:/Users//AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:171:19)
at NodeFsHandler._watchWithNodeFs (file:///C:/Users//AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:325:22)
at NodeFsHandler._handleFile (file:///C:/Users//AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:391:29)
at NodeFsHandler._addToNodeFs (file:///C:/Users/****/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:615:31)
System:
OS: Windows 10 10.0.19045
CPU: (4) x64 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
Binaries:
Node: 26.4.0 - C:\Program Files\nodejs\node.EXE
npm: 11.17.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 150.0.7871.182
Edge: Chromium (150.0.4078.105)
Firefox: 152.0.5 - C:\Program Files\Mozilla Firefox\firefox.exe
Steps to reproduce
I just run netlify dev and this happens every time
Configuration
No response
Environment
netlify dev
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 474
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 53
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from netlify/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area: command: deploy area: docs type: feature
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
type: feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
type: bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·