Make cacheBust a multi task/remove hash from busted url about grunt-cache-bust HOT 6 CLOSED

Cachebusting QA is sometimes a necessity

Your QA environment should be as close to your production environment as possible, which means running tests/QA against concatenated files. Not sure you really need this

removing the grunt-cache-bust URL fragment so it doesn't show up in the links

Great suggestion - hadn't thought about . Have created a separate ticket for this #93

from grunt-cache-bust.

We have a QA environment where we do not compile our handlebars templates into Javascript, but a staging environment where we do compile and concat as you describe. Cachebusting a nonexistent template Js file in our QA environment caused warnings due to it not being found. It may be that we should be compiling the templates in our QA environment as well though.

from grunt-cache-bust.

Okey, thanks for the clarification.

So an option such as shouldRun which is a boolean would be a good approach. That way you can check an environment variable, and if it's QA, then don't run that task.

Sound good?

from grunt-cache-bust.

Another work around within your setup would to have 2 grunt tasks; one for QA and one for everything else. The QA task wouldn't kick off the cacheBust task

from grunt-cache-bust.

I've merged a change to remove the hint fragment when the task is run - #103. I shall be closing this ticket now as the environment problem is specific to your needs and not those of the task

from grunt-cache-bust.

Awesome, thanks!

from grunt-cache-bust.