「フロントエンドで普及が進むビルドツールたち」 インフラエンジニアの祭典「July Tech Festa 2014」でフロントエンドの自動化の話をしてきました。(まだ6月だけど) http://2014.techfesta.jp/
本投稿について Gruntプラグインを紹介していくGrunt Plugins Advent Calendar 2013の12/1の投稿です。 さっき作ったばかりなので、まだすっきりさっぱりしたカレンダーになってますので、どうぞよろしくお願いします。 http://qiita.com/advent-calendar/2013/grunt-plugins grunt-githooksとは GitフックでGruntタスクを実行する仕込みをしてくれるGruntプラグインです。 https://npmjs.org/package/grunt-githooks https://github.com/rhumaric/grunt-githooks Gitフックとは Gitではcommitやpush, rebase, checkoutなどいくつかの操作ができますが、それらの特定の操作を行ったときに、スクリ
NOTE: this guide is out of date. It is only vaild for grunt-browserify@~1.3.0 and its included versions of browserify and browserify-shim. An updated guide is here. It's been a year since I wrote the long Javascript Module Systems article, in which I concluded that CommonJS and Browserify was the best way to write modular javascript for the browser. Over the last year, I've had a chance to test th
Grunt 0.4.3 is now available on npm. This is mostly a bugfix release. Thanks to Jonathan Krause, PatrickJS, Jason Cust, Fabio Crisci, James M. Greene and Mike Pennisi for their pull requests. In addition to closing over 30 issues, we have extracted grunt.util into its own module. As mentioned in the 0.4.2 release, we are in process of deprecating the grunt.util.* API. Task developers who use these
Gruntについて最新の気持ち ::ハブろぐ 上記のブログエントリを読んで非常に今自分が感じていることと共通点を感じました。 Gruntに対する最新の気持ちでは2つの問題提起がされてました。 1. Gruntfile.jsが長すぎる(700行とか) 2. そもそも全部gruntでやらなきゃいけないのか 1.に関しては色んな解決手段があります、ブログの筆者も解決されているようですし、この件に関しては次回のMaintainable Gruntfile.jsで触れます。 最初は2.に関しての、全部gruntでやらなきゃいけないんだっけ、という疑問に関してです。 僕も同じ思いをしてたので、同調してブログを書きます。 gruntについて 言わずと知れたタスクランナーですね、gruntを使うとjavascriptのminifyやmeta cssのコンパイルといったフロントエンドにありがちな作業を自動化
A brief history of Grunt I realized that a task-based build tool with built-in, commonly used tasks was the approach that would work best for me Ben Alman March 2012 Single, global Grunt: $ npm install -g grunt Configuration over code grunt.initConfig({ lint: { src: 'src/<%= pkg.name %>.js' }, concat: { src: [ '<banner:meta.banner>', '<file_strip_banner:src/<%= pkg.name %>.js>' ], dest: '<%= pkg.n
Brunch is a front end build system that lets you get stuff done without needing a 500 line configuration file *cough* Grunt *cough*. However, there’s little in the way of an introduction to setting up Brunch in an existing project - the homepage only shows how to use Brunch with it’s ‘skeleton’ scripts. Thankfully, getting your own project to work with Brunch is simple and painless. Brunch vs Grun
Drop Node.JS 0.8 support New logging (https://github.com/cowboy/node-prolog) A logger to listen to events and output them to the console. Deals with stderr/stdout, or Grunt itself has this built in. node-task (https://github.com/node-task) Tasks as npm modules that can be required and run independent of any task runner (if you want to manually build a compliant config object to execute it). Can pi
Just when you think that you're in control, Just when you think that you've got a hold, Just when you get on a roll, Here it goes, here it goes, here it goes again. OK Go - Here It Goes Again And so the evolution of front-end development continues with Gulp, the new build system that has already garnered praise amongst many web developers. After spending some time reading the docs and playing arou
Gulp-style stream piping in Grunt, or anywhere else Recently a new front-end build tool, Gulp, has been getting quite some attention. What makes it really elegant is its use of Streams to orchestrate the build flow. Since everything is passed down in the buffer, it gets rid of the need to create temporary on-disk files. It already has an active community contributing plugins for it, but still lack
No Need To Grunt, Take A Gulp Of Fresh Air Recently, gulp was released to the world as a rival to the very popular JavaScript task runner, Grunt. Let's take a look at what sets them apart and understand why gulp was created. When it comes to JavaScript task runners, Grunt is king. Well, at least it has been... Earlier this year, the team at Fractal voiced their concerns with Grunt and came up with
Gruntのtaskの実行にかかる時間を劇的に短縮する方法 最近ではGrunt無しでのフロントエンド開発は考えられなくなってきた気がしますが、大抵taskを実行した際に結構時間がかかってしまいます。 Gruntの実行にかかる時間を減らすにはどうすれば良いのか調べてみたら、loadTasks as they are needed to speed up Grunt load time · Issue #975 · gruntjs/gruntのissueに方法がありました。 何に時間がかかっているか taskを走らせた際、何で時間がかかっているのかをtime-gruntで確認してみると、実行しているtask自体ではなくnpmタスク(適切な表現かは分かりませんがGruntプラグインの事です。)の読み込みの方に時間がかかっている事が分かります。 loadNpmTasks()で2秒はかかっている状態
Grunt 0.4.2 is now available on npm. This release should address a lot of issues for Windows developers, such as pipe-redirection, console output and BOM preservation. Besides a number of bug fixes, we have made a few decisions going forward regarding external dependencies in Grunt. These external libraries are deprecated and should now be required as npm modules: Use glob instead of grunt.file.gl
What we'll cover reading time: approx. 19mins What is Grunt? Installation Package.json Dependencies Gruntfile.js Sass RequireJS JSHint Jasmine BDD Image Minification HTML Minification Registering tasks Watching files Our full Grunt file Conclusion What is Grunt? Grunt is a JavaScript based task runner. What this means is that it will help you spend less time manually running tasks that can be auto
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く