#Hammer vs codekit install

#Hammer vs codekit install

Make a shell script to install Grunt and your dependencies so someone can easily pull down your branch, run the shell script and be ready to contribute:

Ignore the node_modules/ dir, it doesn’t belong in the repo, makes a mess, and can cause strange Grunt bugs I found a couple of things pretty early on that this can be made much smoother for your fellow project members: This is especially true If you’re running with Grunt as part of your repo and you have to set it up every time you make a build for a project. The installation work for Grunt is the most annoying part of the process, given that it’s so repetitive and tedious. I’ve actually been using Grunt for a lot of my projects at work. – If you want to use SASS in combination with LiveReload and need style injection, which means that the CSS gets updated without a page reload, than you need to do it like described here: /2013/06/subtle-live-reloading-with-grunt-and-compass If you want to minify multiple JS files, use this syntax: It’s basically the same with the same configuration variables. you use mixins like border-radius, which you really should), install grunt-contrib-compass instead of the mentioned grunt-contrib-sass. However I ran into a few problems, which I’d like to share here: Before I have used Sublime Text’s LiveReload package, but unfortunately it is pretty buggy and crashed my editor regularly. Especially LiveReload finally works properly for me. But now, after some hassles and tweaks, it runs like a charm and I’m very glad that I gave it a try. It finally convinced me to give Grunt a try, since every time I wanted to install it so far, I was scared by the guides.