Opened 7 months ago
#49275 new enhancement
Errors deleting plugins while using npm run dev
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | Cc: |
Description
Not sure if this is something related to my setup only.
I'm usually working with npm run dev / grunt watch --dev. Unfortunately, if testing/creating patches includes adding and removing plugins/themes it seems that the process kinda breaks 😁.
Since watch is trying to keep track of everything inside /wp-content and not only related core files Fatal Errors are popping up due to either permission (not sure why as there shouldn't be a problem) or because files had already been deleted by the Plugin uninstall action resulting in pretty much a mess with folders not being able to be completely removed and sometimes making the process hang there.
The only way that I've found out of it is to stop the process, manually delete anything that is needed and get back to a default clean state of wp-content and re-run npm run dev again.
Is there a way to maybe only "watch" the wp-content files that core has and nothing else?
To test this, simply run npm run dev and then install & uninstall a plugin via wp-admin ( or have it installed already then start npm run dev and uninstall the plugin via wp-admin ).
