gh-pages cache does not clear automatically after running markbind deploy manually

[gerteck]

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

#2547 #2562

Tell us about your environment

Mac OS

MarkBind version

6.1.0

Describe the bug and the steps to reproduce it

Package gh-pages uses a cache directory before pushing to github for deployment, and markbind does not clean up this directory after deploying.

This is a bit unsightly and can cause issues when redeploying as sometimes it gets copied again as assets when we re-run deploy.

Let's clean up the cache and remove the clutter.

The gh-pages and @types dev dependency are also out of sync, let's take the chance to bump the versions.

Expected behavior

No response

Anything else?

No response

[damithc]

Thanks for fixing this, @gerteck
I also faced this from time to time, and reseted to inserting an rm ... command in front of my deploy command :-p

[gerteck]

Thanks for fixing this, @gerteck I also faced this from time to time, and reseted to inserting an rm ... command in front of my deploy command :-p

Have rectified the issue! Although the directory path node_modules/.cache may still persist after cleaning, but it should be emptied and be an empty folder after deployment so no assets are copied.