Please replace with a clear and descriptive title
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- cli
Research direction
Start by reproducing netlify dev on Windows 11 with the reported project setup, then trace the file-watching path from the netlify dev entry point to the Chokidar stack shown in the error. Determine why it attempts to watch C:\Users\bdrap\Application Data; done means the CLI remains running and serves the project without terminating unexpectedly.
Written by the indexing model from the issue text.
Description
Describe the bug
after successfully connecting to a project, I ran the prompt netlify dev. It worked shortly as shown below:
PS C:\Users\bdrap> netlify dev
⬥ Injecting environment variable values for all scopes
⬥ No app server detected. Using simple static server
⬥ Running static server from "bdrap.next"
⬥ Setting up local dev server
⬥ Static server listening to 3999
╭─────────────────────── ⬥ ────────────────────────╮
│ │
│ Local dev server ready: http://localhost:8888 │
│ │
╰───────────────────────────────────────────────────╯
» Error: Netlify CLI has terminated unexpectedly.
Steps to reproduce
after connecting to your netlify project, run netlify dev and I immediately had my CLI discnonected
Configuration
Error: EPERM: operation not permitted, watch 'C:\Users\bdrap\Application Data'
at FSWatcher. (node:internal/fs/watchers:321:19)
at watch (node:fs:2548:36)
at createFsWatchInstance (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:126:16)
at setFsWatchListener (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:171:19)
at NodeFsHandler._watchWithNodeFs (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:325:22)
at NodeFsHandler._handleDir (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:546:27)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async NodeFsHandler._addToNodeFs (file:///C:/Users/bdrap/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/chokidar/esm/handler.js:591:26)
Environment
System:
OS: Windows 11 10.0.26200
CPU: (16) x64 AMD Ryzen 7 8745HS w/ Radeon 780M Graphics
Memory: 36.70 GB / 61.78 GB
Binaries:
Node: 24.18.0 - C:\Program Files\nodejs\node.EXE
npm: 11.17.0 - C:\Program Files\nodejs\npm.CMD
- 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 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·