I am trying to setup a GruntJS build pipeline for one my side projects and ran into a very interesting warning today, shown below.
What was weird was that this warning/error only started when I added my task to compile my typescript code. If I called the default task, which did not compile the Typescript code, everything worked as expected. Of course because the Typescript task was failing I assumed the error had something to do w/ its configuration. However, as you can see my Typescript setup is pretty simple
Because my setup looked right I thought it would be a smart idea to run the task with the verbose output via the ‘grunt typescript –v’ command. The second I ran this I saw the issue…
The ‘Running “typescript” task goes on and on until we hit our stack over flow.
I immediately changed focus from my Typescript configuration to my Task configuration and saw the issue.
Looking at my Task setup above I saw the issue. It is bad idea to name your Grunt task the same as your one of the target tasks in your config…DOH.
After changing the name of my Grunt tasks as follows, the world was a happy place.
The moral of the story is 2 fold.
- Do NOT name your Grunt task the same as your configuration element
- Use the –v option to see what is really going on when a Grunt Task fails.
Till next time,
P.S. If you want to learn more about Knockout watch my Pluralsight Course on Knockout JS
P.S.S. If you want to learn how to transition your XAML skills to HTML you can watch my course on Html for the XAML Developer
08-18-2013 7:37 AM