CODEKIT PARA WINDOWS INSTALL
I’ll give it a try on my next project, but I think the command line is too bureaucratic, you have to memorize several commands, install several things – and it’s not clear to me what is the utility of those directories, like (absent on the github project).Īs an idea for the next articles, I miss a better explanation of a workflow using Yeoman – one that goes beyond the simple running of commands, one that installs then interacts with the files in a real project, where to start, what commands should be run (the essential ones, not the theatrical ones used to impress your boss)Ĭhris, thank you so much for this article. That gave me a good perspective of the use of Grunt. I feel more alleviated knowing I’m not the only one that sees those garish tools with fancy names. “Grunt is one of those fancy newfangled things that all the cool kids seem to be using but at first glance feels strange and intimidating. tools, which will house our js in the future. To be more future-minded, we’ll move sass under
Set your source and destination files as a module and call those in your subsequent config blocks: So each time you add a new plugin to Grunt, just add a new line to this file. You call this script by going to your project root (same place you’d want to run Grunt from) and running sh grunt-deps.sh. Npm install grunt-contrib-concat -save-dev
# Above is nice because even if the user already has these installed, it won’t do anything unnecessary. 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.
0 kommentar(er)
