I've noticed an issue with the way the grunt tasks are setup by default for this project. The uglify task reads out every JS file in library/js and then writes library/js/scripts.min.js. What happens when you are developing a theme and running grunt frequently is that each time, grunt collects the previously generated scripts.min.js file and rolls it into the new scripts.min.js file. As a result, not only do you very quickly end up with an enormous JS file, but memory usage balloons out.
Please consider either putting the build output into its own directory, or cleaning the source directories of previous build artefacts before each build.
I've noticed an issue with the way the grunt tasks are setup by default for this project. The
uglify
task reads out every JS file inlibrary/js
and then writeslibrary/js/scripts.min.js
. What happens when you are developing a theme and running grunt frequently is that each time, grunt collects the previously generatedscripts.min.js
file and rolls it into the newscripts.min.js
file. As a result, not only do you very quickly end up with an enormous JS file, but memory usage balloons out.Please consider either putting the build output into its own directory, or cleaning the source directories of previous build artefacts before each build.