Minified version
matt-bailey opened this issue · comments
Any chance of including a minified version of the file?
That way I can skip a step in my grunt workflow, i.e. just copy the file straight to wherever I need it, rather than having to uglify it first.
It would be a "nice-to-have" convenience, though it would put the onus of remembering to minify before pushing/releasing onto the plugin developer(s). Although this is admittedly an embarrassingly scriptable process, it could be mildly disruptive to the plugin development process going forward in that it would force a habit change.
@briancherne will ultimately decide whether or not the convenience of an unknown subset of the plugin users is worth further amending his development process, but in the meantime, interested folks can '+1' or subscribe to this issue as a sort of implicit vote (one can also '-1' if for any reason one has strong objections).
As it happens, for the particular project I'm working on I ended up concatenating the plugins before minifying them. So I didn't require a minified source version in the end.
However, plugin developers providing a standard and minified version of a script is still a good idea IMO.
Agreed though, that it's easier if the developer is already in the habit of working with a src/dist/tests type of automated workflow.
I can see the benefit of having a standard/approved minified version (I offer one on my web site, not tied to the github repo), but as @usmonster mentions it would require a change in development process... thus work.
I'd like to see 3 people "+1" this issue/feature request before we add it, or close it after a year of inactivity.
+1
+1
+1
+1
FYI, a minified file will be included in the upcoming version, so the poll requires no more votes. :) Thanks to all who made the desire for this feature known!
+1