If you’re unfamiliar with regular expressions, you can play around with this one here. In this example, the regular expression matches all files that are in the directory less and have a.
#USING GUARD LIVERELOAD INSTALL#
watch takes a regular expression that matches all files in the project. It is not possible to install guard-livereload 2.5.2 on Ruby 1.8.7 because it depends on guard 2.8, which requires Ruby 1.9.
#USING GUARD LIVERELOAD HOW TO#
This example shows a guard :less block with a watch method. In my previous blog post, I have written about how to use LiveReload Chrome extension, with Guard and some Ruby gems to make a web page automatically reload. This may seem a little confusing, but you’ll understand in a minute. It uses regular expressions and the watch method inside of a block. There are 2 ways to do this: Use a LiveReload plugin in your browser Add a special snippet to your web page (automatically or manually) 1.
For this to work, guard-livereload has to somehow send the livereload.js script to your browser. Less’ config is a little different than guard-coffeescript and guard-sass. Livereload tells your browser to refresh when files change. When you save any *.coffee file in the coffee directory, Guard will compile it to the js directory using the same name. Notice in the terminal that when you save the file, it generates the JavaScript in the js directory: guard(main)>Ģ0:54:21 - INFO - Compile coffee/ffeeĢ0:54:21 - INFO - 08:54:21 PM Successfully generated js/test.js Start up guard and see it watch our files: $ bundle exec guardĪdd a little CoffeeScript to our project and save: # file: coffee/ffee This way, CoffeeScript lives in the coffee directory and is compiled to the js directory. Notice that we added :output to the options. (We recommend guard-livereload, until LiveReload 2 comes to your platform.), It means that the.
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' Please make sure that a compatible LiveReload server is running. Guard 'coffeescript', :input => 'app/assets/javascripts' Mentioning what youre doing and how (local/remote livereload, which browser, which OS, which extension, with Rack. See for details visit to get help and vote for new features. Let’s take a look inside: # A sample Guardfile Provides Chrome browser integration for the official LiveReload apps (Mac & Windows) and third-parties like guard-livereload and yeoman. 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. When I fire up guard in a terminal window, livereload seems to reload the browser page, but when I use foreman, there is no response. (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 '' 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. Installing/Using I will be going with the assumption that you have ruby installed locally. You’ll need to add 2 gems to your Gemfile: rack-livereload and guard-livereload. LiveReloading is a completely different thing but it’s easy to go there. This plugin is part of a ruby gem called Guard. And now you must be thinking Ok, all this is cool but I was expecting that Sinatra-reload would be somewhat related to that LiveReload does, aka, trigger browser refreshing.
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. This process of saving and reloading the browser can be eased using a plugin called Guard-LiveReload. Next, you have to decide which plugins you want. I usually set up rails to use Guard to run my tests when I change a file or so that I can just hit enter to run all of my tests, but that requires that I manually run bundle exec guard every time I start my rails server.Installing Guard is as easy as gem install guard.
0 kommentar(er)
