Prohibit 'globalstrict' jshint option in favor of 'strict', for src and demo files.

[thgreasi]

In an effort to improve the situation described in #133.

[alexilyaev]

+1

[douglasduteil]

Following #133 (comment)

We can add a concatenation process with the ngmin.
It'll add on the header :

(function() { 'use strict';
// or 
(function(window, document, undefined) { 'use strict';

and on the footer :

})();
// or 
})(window, document);

Inspired by loader.prefix and angular.prefix

[thgreasi]

I guess it's better to follow the angularjs pattern.
That way we can still have globalstrict and we might even use the prefix & suffix for something more that a closure at some point.
My only concern is that some developers, in order to try a library, prefer to just copy&paste the js file in the SRC directory, instead of using grunt install or making their own build. These developers will still face the problem described in #133.

[douglasduteil]

My only concern is that some developers, in order to try a library, prefer to just copy&paste the js file in the SRC directory, instead of using grunt install or making their only build.

you mean bower install right ?

[douglasduteil]

Yeah I think using the prefix & suffix will allow them to do as they want.
The master ant srcX.Y.Z tag will content sources without use strict
But the official version vX.Y.Z will still have it.

[thgreasi]

Yes, sorry bower install.