Request: Have the option for two compiled JS files. One has all the application code and the other that is compiled less frequently that has all the libraries to reduce uglify time

[odellcraig]

The reason being that if you end up using a lot of libraries, uglify can take a really long time. Seems like the solution would be to uglify the library files infrequently.

[joshdmiller]

I think the solution is probably in an incremental build, which I hope to accomplish by replacing grunt with something more modern.

That said, uglify only runs when you do a compile - not when you do a build. The latter is meant for development, which is why expensive steps like uglification are skipped. Are you running compile during active development? If so, why did you choose to do so?

[odellcraig]

I only use it when deploying, but I deploy a couple times a day. It really wouldn't save much time - uglify only takes a few minutes (after I added a huge graphing library).

One other thing I was thinking about - is there a way to run a grunt watch without karma? The reason being that if the test suite gets big then it would increase the cycle time quite a bit on the watch. It would be nice to have a watch that did everything but run tests.

[joshdmiller]

There isn't such a feature, but it's simple for you implement: https://github.com/ngbp/ngbp/blob/v0.3.2-release/Gruntfile.js#L560. Either remove karma from your watch or create a new watch task that doesn't run karma.

[odellcraig]

Cool. Thanks, Josh.

On Thu, Dec 3, 2015 at 1:43 PM Josh David Miller notifications@github.com
wrote:

There isn't such a feature, but it's simple for you implement:
https://github.com/ngbp/ngbp/blob/v0.3.2-release/Gruntfile.js#L560.
Either remove karma from your watch or create a new watch task that doesn't
run karma.

—
Reply to this email directly or view it on GitHub
#413 (comment).