[Solved] Error: EBUSY: resource busy or locked, rmdir

While Running npm run start I was facing Error: EBUSY: resource busy or locked, rmdir in angular you are facing same error? Then You are in right place. In this article, we will try to figure out how this error occurs and what are the possible fixes for this error. First of all, let’s explore how this error occurs.

What is Error: EBUSY: resource busy or locked, rmdir error?

While Running npm run start I was facing this error.

Error: EBUSY: resource busy or locked, rmdir

How To Fix Error: EBUSY: resource busy or locked, rmdir Error?

Solution 1: Run cache verify

To Fix Error: EBUSY: resource busy or locked, rmdir Error You just need to verify your npm cache. You can run this command to cache verify.

npm cache verify

And now you can run the start watching without any error. Thanks.

Solution 2: Kill Terminal

This error usually occurs whenever multiple terminals open with the same projects. Whenever You are using VS Code. Just Kill All Terminal And Reopen New Terminal will resolve this error.

Solution 3: Install the npm cache

First Of all, You need to delete your package-lock file manually. Now You need to Clear Your NPM cache by running this command.

npm cache clean

And then you need to install the cache by running this command.

npm install --cache

Now, Your error must be solved.

Conclusion

It’s all About this error. I hope We Have solved Your error. Comment below with Your thoughts and your queries. Also, Comment below on which solution worked for you.

Also, Read

• ImportError: No module named apt_pkg
• ImportError: cannot import name ‘Celery’ from ‘celery’
• TypeError: store.get is not a function
• ‘EntryPoints’ object has no attribute ‘get’
• failed to initialize editor in android studio