EBUSY: resource busy or locked when deleting the dir that Nuxt ran in
Open
Nobody has claimed this yet.
bug
nuxt
v2
windows
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Environment
Windows, Nuxt 3
Reproduction
https://github.com/dword-design/try-nuxt-resource-busy
See GitHub Actions output.
Describe the bug
Looks like Nuxt has some files locked after running on Windows, which is why I cannot delete the directory anymore. Works fine on other OSes.
Additional context
No response
Logs
https://github.com/dword-design/try-nuxt-resource-busy/actions
[Error: EBUSY: resource busy or locked, rmdir 'D:\a\try-nuxt-resource-busy\try-nuxt-resource-busy\foo'] {
errno: -4082,
code: 'EBUSY',
syscall: 'rmdir',
path: 'D:\\a\\try-nuxt-resource-busy\\try-nuxt-resource-busy\\foo'
}
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.
Research direction
Start by reproducing the issue from the linked try-nuxt-resource-busy repository on Windows and review the linked GitHub Actions output. Trace what remains open after Nuxt 3 runs, then verify that the generated directory can be deleted without EBUSY; the issue does not name a source file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100