Archive for February, 2014

Auto-generate modularized #grunt configuration files

I wrote a Grunt task which will take your big, fat grunt configuration object and automatically generate separate files to store the task configuration objects in: grunt-generate-configs

The task will parse your grunt configuration object and automatically create files for each task.
Continue reading


Best way to handle large grunt files

I love Grunt. Each project I’ve done last year I’ve used it to automate linting, building, testing, etc. There’s just one thing which keeps on bothering me: once a project grows, so does the grunt file. I just keep on finding new grunt plugins and adding them to my projects. With every plugin, task configuration and declarations are added to the Grunt file and its size just keeps on growing, making it very messy and hard to maintain IMO.

TL;WR (too long;won’t read)

We’re having a discussion on the best way to manage large grunt files in this thread of the yeoman generator-webapp project. Let us know what you think!

So, what’s it all about?

To me, the best way to manage grunt task configurations is by splitting it all up into several files.

I wrote a module load-grunt-configs which loads your grunt task configuration objects from files in a directory.
Continue reading

Load #gruntjs task configurations from separate files.

Grunt files tend to grow fast due to big amount of tasks and their configuration objects. I created a module load-grunt-configs that allows you to split your Grunt task configuration objects into separate files any way you choose. There are similar modules that allow you to the same, but with grunt-load-configs you can configure targets for a single task in multiple files.

This means you no longer need to group all task targets into a single file, but can split them up according to their task dependencies.

See for examples and usage.

Continue reading

%d bloggers like this: