Skip to main content

My journey in discovering Grunt: A JavaScript Task Runner

Some weeks ago, I was looking at the html2canvas library on GitHub. I wanted to test the code so I decided to clone it to my local repository. However the source code is split over multiple files, so if you want to use it inside your application you have to build it first.
My first naïve attempt, was just running the grunt.js file as found in the project directory. This failed with the following message:
clip_image002
Going back to the project site, I found that you have to use Grunt(a node.js plugin) for building:
The library uses grunt for building. Alternatively, you can download the latest build from here.
Run the full build process (including lint, qunit and webdriver tests):
$ grunt
Ok, let’s try this. I opened a command window and tried to execute the command(notice that I already have node.js installed on my machine):

npm install -g grunt-cli

This will put the grunt command in your system path, allowing it to be run from any directory.

Let’s now run the grunt command(you can use both grunt and grunt.cmd):

clip_image002[5]

Woops. No success. I figured out that I was using a more recent version of Grunt than the project was using. In the meanwhile the convention had changed and instead of having a grunt.js file in your project directory, you need to name it gruntfile.js(More info here: http://gruntjs.com/getting-started).

clip_image002[7]

The Gruntfile.js or Gruntfile.coffee file is a valid JavaScript or CoffeeScript file that belongs in the root directory of your project, next to the package.json file, and should be committed with your project source.

A Gruntfile is comprised of the following parts:
· The "wrapper" function
· Project and task configuration
· Loading grunt plugins and tasks
· Custom tasks
Run the command again, still failure:


image

Grunt itself is doing nothing, it only loads a set of plugins and tasks and execute them. It seems that grunt tried to execute some tasks that I didn’t install. So let’s install the missing packages and try again:

 image

Ok, last attempt, this time we finally got Grunt working:

image

And now I have a nice new tool in my toolbox.

image

For a good introduction on Grunt, I can recommend reading http://www.elijahmanor.com/2013/04/angry-birds-of-javascript-mighty-eagle.html

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...