Minify on Save - ONLY if a minified file already exists

[minig0d]

🚀 Feature Request

Is your feature request related to a problem? Please describe.

• I definitely don't want to enable minifying every single file I save... but yet love the convenience of minify on save...

---

Describe the solution you'd like

• I forgot what extension I used to use before switching to this one, but it had a really helpful feature that would only minify on save IF the .min file already existed. Which is perfect because it's effectively that triggering minify on the file once kind of opts you into it (acknowledges that this is a file the user wants to be a part of minifying, in general) and when the file is modified and saved, it's evident that the user is trying to save an updated version of it. To me it's the perfect win-win! (and should be very easy to implement too!)

---

Describe alternatives you've considered

*

---

Additional context

*

[welcome[bot]]

Thanks for opening your first issue in Josee9988/project-template! Be sure to follow the issue template and provide every bit of information to help the developers!

[Josee9988]

Hey, it definitely makes sense! I will love to add this feature. But this will have to wait as I am no longer maintaining this project as I am focusing on other projects and university.

But I will make it happen sooner or later.

I hope you understand!! 🙏

[Cube707]

Hello,

there is also the feature request under #131 which asks for an easy way to tell minify what files to just ignore. As both of these requests are quite similar in that the user wants to prevent some unnecessary files from being minified while not having to manually trigger the minifyer for worked on files, these could maybe be combined into a single feature.

Would the "define ignore patters" approach already suite your workflow?

[Josee9988]

Yep #131 should fix this one

[Josee9988]

I'll see if I can buy some free time and add this feature, at least.

[minig0d]

Hello,

there is also the feature request under #131 which asks for an easy way to tell minify what files to just ignore. As both of these requests are quite similar in that the user wants to prevent some unnecessary files from being minified while not having to manually trigger the minifyer for worked on files, these could maybe be combined into a single feature.

Would the "define ignore patters" approach already suite your workflow?

It would be better than nothing but no.... this is based on an assumption that 100% of the files I edit should have a minified version created... I edit TONS of different files for all different purposes. I would have to break into separate folder level settings because even at the workspace-level I don't minify everything. I only minify files I edit ad-hoc direct for web publishing...

Honestly, I if I was thinking about every file being minified, that would seem more like a better use of webpack, grunt, or gulp... In my opinion, the benefit for it is when doing ad-hoc editing... Ex. If I'm trying to make minor tweaks on a production website, making a tiny change, then making a second tiny change, then making a third... I have to re-minify between each time for the changes to go live.

I don't know... maybe if my workspaces were more organized.... but I tend to use a couple workspaces for everything.

I think as long as the setting worked correctly as a "folder" level-setting I could make it work because I could specifically create folder-level settings to enable it a a folder-level only in specific folders.... but I would never enable the feature globally as a workspace or user config. I just edit so many different types of files for so many reasons (ex. a snippet of css/js here and there that aren't part of formal projects). But in all of these cases, the same logic holds true... if there is a .min.js or .min.css file in the folder, I also want to update the minified version. 100% of the time. I could never say the same about a user/workspace/folder level setting.

And I've never tried to code anything that used user provided include/exclusionary patterns, but I'd imagine it's a heck of a lot less work to just do an async file exists test vs. interpreting globs or utilizing .ignore files etc. (I.e. selfishly my idea will probably take 30 minutes at most.... glob/ignore 5x that) :)

[supersuphot]

I move from Minify by HookyQR and I find this feature very useful. It only minifies if the *.min.ext file exists. I wish this feature could be implemented in other extensions as well.