[4.0] Let build tools always start clean

[dgrammatiko]

Pull Request for Issue # .

Summary of Changes

• Clean all the Joomla core media folders each time that npm install is called

Testing Instructions

Before applying the patch make a backup of your current media folder
Apply the patch
Run npm install
Compare the backup folder with the current media

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Documentation Changes Required

@wilsonge this can wait till 4.0 is released

[brianteeman]

Considering your previous comment is it safe to remove all of vendor and should it not be vendor\xxxxx

[dgrammatiko]

Considering your previous comment is it safe to remove all of vendor and should it not be vendor\xxxxx

Yeah, probably I should target only the vendor folders that Joomla delivers. That said the existing code already discards the vendor folder, so I guess I need to fine-tune that part

[richard67]

Will someone remember to maintain this hardcoded list if some new extension which has assets will be added or removed in future?

[dgrammatiko]

This file is the backbone of the build tools but you're right there are way too many hardcoded things here. Will refactor it so it's easier for maintenance

[RickR2H]

I have tested this item ✅ successfully on a964dec

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35048.}

[RickR2H]

I have tested this item ✅ successfully on a964dec

Patch works. On loding the article the description gets truncated to 160 characters.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35048.}

[richard67]

I have tested this item ✅ successfully on a964dec

Patch works. On loding the article the description gets truncated to 160 characters.

@RickR2H Can it be that this second test here was meant for another PR? The comment below your test result doesn't fit to this PR here.

[RickR2H]

@richard67 My browser had some hick ups. Sorry for the confusion.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35048.}

[RickR2H]

I have not tested this item.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35048.}

[RickR2H]

@dgrammatiko how can I verify that the patch works? Should there be a difference between the backed up folder and the newly generated?

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35048.}

[dgrammatiko]

how can I verify that the patch works? Should there be a difference between the backed up folder

There should be identical (assuming that the backup didn't had .gz files, if it did you need to run the npm run compress iirc)

[dgrammatiko]

This PR is not needed urgently so I will switch it to draft and we can check it back after the GA

[dgrammatiko]

@RickR2H @richard67 I've opened a new PR with the code from this one plus a replacement of a node package for the watch functionality. Please test #35198