Notice that we added :output to the options. That’s very nice, but we keep our CoffeeScript in a different directory than the compiled JavaScript, so let’s change the file: guard 'coffeescript', :input => 'coffee', :output => 'js' Guard 'coffeescript', :input => 'app/assets/javascripts' Let’s take a look inside: # A sample Guardfile This generates a configuration file ( Guardfile) for your “guards” (plugins). Let’s initialize Guard with CoffeeScript: $ bundle exec guard init coffeescript With guard-coffeescript you no longer have to decide between ugly JavaScript or an ugly compile process with CoffeeScript. Admit it, and the Ruby-esque syntax of CoffeeScript lured you from the beginning. Also, the gem therubyracer is required by guard-less, but not used as a dependency, so we have to add it ourselves. (see issue #16) You can try it without the git option, but I cannot guarantee an error-free installation. This may change, but right now, this is how it is. Note: At this point in time, it is necessary to build the guard-less gem from git because the maintainers have not pushed the latest version to RubyGems. Gem 'guard-less', git: 'git:///guard/guard-less.git' Here’s what your Gemfile should look like if you’re using all of the plugins: source ''
#Guard livereload windows how to
Once you learn how to set up these 5 plugins, you’ll be able to setup the other 267+ available guard plugins.įor most projects, it’s advisable to have a Gemfile for dependencies. In this tutorial, we’re going to discuss the following plugins: (you will need to install them: gem install PLUGIN)Įach plugin is a little different, but also a lot the same. Next, you have to decide which plugins you want. Installing Guard is as easy as gem install guard.
0 kommentar(er)
