I'm using your plugin in the build script for one of my projects. I agree that sometimes the optimization steps are just too complicated to rely on the automatic concatenation & minification. This grunt task is exactly what I need.
However I just found out a little issue: in the HTML files, if I have multiple build:remove blocks, only the last block is removed. Looking into your code, I think it is because the blocks are stored in a hash object with build tags as keys, therefore the same build:remove tag is replaced with later-found ones.
My current workaround is adding a dummy parameter: e.g: to make the block's tag unique.
I think the plugin should make the multiple :remove block issue transparent to users by adding a unique id for the hash key (appending line number for example).
Hi,
I'm using your plugin in the build script for one of my projects. I agree that sometimes the optimization steps are just too complicated to rely on the automatic concatenation & minification. This grunt task is exactly what I need.
However I just found out a little issue: in the HTML files, if I have multiple build:remove blocks, only the last block is removed. Looking into your code, I think it is because the blocks are stored in a hash object with build tags as keys, therefore the same build:remove tag is replaced with later-found ones.
My current workaround is adding a dummy parameter: e.g: to make the block's tag unique.
I think the plugin should make the multiple :remove block issue transparent to users by adding a unique id for the hash key (appending line number for example).
I leave this for your consideration.
BTW, thanks for the nice plugin. :)