srakathai.blogg.se - Using guard livereload

USING GUARD LIVERELOAD INSTALL

This prevents a flash of unstyled content. Our workaround is to add a temporary element for the imported stylesheet we're trying to reload, wait 200ms to make sure WebKit loads the new file, then remove and recreate the rule. Modifying a CSS rule to reference a not-yet-cached file causes WebKit to lose all document styles, so we have to apply a workaround that causes a lag. Live reloading of imported stylesheets has a 200ms lag.

reloadMissingCSS: prevent reload of CSS when changed stylesheet isn't found in page (default: true).

isChromeExtension: reload chrome runtime instead of page when true (default: false).

handshake_timeout: timeout for a protocol handshake to be completed after a connection attempt mostly only needed if you're running an interactive debugger on your web socket server.

mindelay, maxdelay: range of reconnection delays (if livereload.js cannot connect to the server, it will attempt to reconnect with increasing delays) defaults to 1,000 ms minimum and 60,000 ms maximum.

path: optional path to livereload server (default: 'livereload').

host: the host that runs a LiveReload server required if specifying LiveReloadOptions, otherwise will be autodetected as the origin of the tag.

The set of supported options is the same for both methods: If the dictionary is specified, livereload.js does not even try looking for its tag. Options can either be specified as query parameters of the tag's source URL, or as a global window.LiveReloadOptions dictionary. This approach enables LiveReload when viewing the web page from other devices on the network: LiveReload 2 server listens on port 35729 and serves livereload.js over HTTP (besides speaking the web socket protocol on the same port).Ī slightly smarter way is to use the host name of the current page, assuming that it is being served from the same computer. This script is meant to be included into the web pages you want to monitor, like this: The reason you need to specify LiveReloadOptions is that livereload.js won't be able to find its tag and would normally bail out with an error message. Note that livereload-js package uses window and document globals, so won't run under Node.js environment.

USING GUARD LIVERELOAD INSTALL

Including livereload.js into your Browserify bundle probably makes no sense, because livereload.js isn't something you would ship to production.īut if you insist and you know what you're doing, you can install LiveReload via npm: npm install livereload-js -saveĪnd then add this to your bundle: window.LiveReloadOptions = This gives you a component containing a single script file, dist/livereload.js. Installation: bower install livereload-js -save-dev (But, to reiterate: the preferred method is to avoid installing it altogether, and instead use the one bundled with your LiveReload server/app/tool.) Live image reloading (, background-image and border-image properties, both inline and in stylesheets).We require LiveReload server vendors to distribute livereload.js as part of their apps or tools.Īn old version of this script is also bundled with the LiveReload browser extensions, but it's not getting updated and only serves for compatibility with very old clients. If you are developing a LiveReload server, see dist/livereload.js for the latest version built using the sources in this repository. It gets change notifications from a LiveReload server and applies them to the browser.

This repository contains a JavaScript file implementing the client side of the LiveReload protocol.

interested in hacking on livereload.js or want to understand it better.using a server that doesn't document the usage of livereload.js.

When your server is running, you can typically access the script at. Most LiveReload server vendors will serve livereload.js on the LiveReload port. You should use the copy of livereload.js script bundled with your server, because it's guaranteed to be compatible, and may be customized for that server. If you are a web developer looking to use LiveReload, you should refer to your LiveReload server/app/tool's documentation, rather that this repository.

you can even write your own refer to the LiveReload protocol.

The server notifies the client whenever a change is made. When any other file is modified, the page is reloaded. When a CSS or an image file is modified, it is live-refreshed without reloading the page. The client connects to a LiveReload server via web sockets and listens for incoming change notifications. This repository (livereload.js) implements the client side of the protocol.

To use LiveReload, you need a client (this script) in your browser and a server running on your development machine. LiveReload is a tool for web developers and designers.