coastalsetr.blogg.se

Codekit grunt
Codekit grunt















If you have no idea what this is don’t worry for now. Grunt.loadNpmTasks('grunt-contrib-watch') Grunt.loadNpmTasks('grunt-contrib-sass') Copy and paste this into the Gruntfile.js file:.Copy and paste this into the package.json file:.One called ‘package.json’ and the other called ‘Gruntfile.js’ In the root of your project make two blank files.Grunt users, you’ll know which bits to skip, for everyone else, crack open your text editor of choice and your Terminal (sorry Windows users). All you need (hopefully) is to follow along and do a little cut and paste. And how about automatic live reloading of changes in the browser to boot? If you know nothing of Grunt, fear not, it’s perhaps a topic for another day. Well, I think there is a simpler way to source mapping glory by using Grunt to compile your Sass. Why I hear you (one person if I’m lucky) cry? I’ve therefore omitted that section from this rewrite.

Codekit grunt how to#

There are now plenty of other resources on the Net to explain how to get this up and running from the command line using the Sass watch command. To get the pre-release version of Sass run sudo gem install sass –pre in the CLI. In order to get this working with Sass, you’ll need Sass 3.3 (pre-release at the time of writing).

codekit grunt

Safari 6.1+ and the latest versions of Chrome (use v29+ of Chrome, if your ‘stable’ version isn’t yet at v29, grab the ‘Beta’ or ‘Dev’ version here: ) use ‘source maps’ for Sass debugging.

codekit grunt

Minor update : For those looking for Compass compatibility with source maps, that fine fellow Dennis Gaebel has put together a small project on GitHub providing demo configurations for Compass based source maps (there are branches for Grunt, Gulp, CodeKit 2).















Codekit grunt