This allows you to define an order dependency for your javascripts. This tells codekit that the contents of b.js will go after the contents of a.js. Using codekit, I can define a file app.js that contains codekit-specific statements used to import the contents of a.js and b.js for merge and minification. Let’s say that I want to build several js files in my current directory into one file:. Since the team would have to adopt codekit for my preprocessors, it would be easy to also configure Codekit for my JS build system. I ended up going with Codekit for this, since I already use it for SLIM and SASS compilation. This is hard for a PHP-based team that detests extra steps in their dev process rightly so. This means that you need to choose a toolset that accommodates your team’s tech experience and competence. The hard part is not picking a build system, but picking one that your team would adopt. * You could roll your own bash script using YUI or Google Closure compiler for building * There’s some ugly php based scripts that could be run * Ruby guard could be used for a custom build system * Require.js has an optimizer (I haven’t used it) that seems applicable
Codekit build scripts code#
* Grunt.js could be used for Uglifying code * Rails comes with its awesome asset pipeline that makes devs spoiled (yes, I’m jealous since I am forced to code PHP) and packages the JS up into a tight, content-hashed ball.
There are many tools available for building assets for production: I was on the hunt for several setups and here’s what I settled on. Recently, I was building out a single-page app for YouNow and needed a build system to merge and minify my JS files.
I’ve been using Codekit since it was in pre-release beta and haven’t looked back.
0 kommentar(er)
