neromoving.blogg.se - Alternative to livereload

Alternative to livereload install#
Alternative to livereload full#
Alternative to livereload code#

spdy) ( -no-css-inject to reload page on css change instead of injecting the changes ( Dependencies updated to get rid of vulnerabilities in deps -https-module=MODULE_NAME to specify custom HTTPS module (e.g.We welcome contributions! See CONTRIBUTING.md for details.

Alternative to livereload full#

CSS files can be refreshed without a full page reload by finding the referenced stylesheets from the DOM and tricking the browser to fetch and parse them again. This script establishes the web socket connection and listens to the reload requests.

Alternative to livereload code#

In order for the client side to support this, the server injects a small piece of JavaScript code to each requested html file. It also watches the files for changes and when that happens, it sends a message through a web socket connection to the browser instructing it to reload. The server is a simple node app that serves the working directory and its subdirectories. Where MS is time in milliseconds to wait before issuing a reload.

Reload works but changes are missing or outdated.If it’s still not working, file an issue. Note that you will need a browser that supports WebSockets. Open your browser’s console: there should be a message at the top stating that live reload is enabled.The keys are the same as the keys in options for tls.createServer.

The module must export an object that will be used to configure a HTTPS server. In order to enable HTTPS support, you’ll need to create a configuration module. Var liveServer = require ( "live-server" ) var params = liveServer. If a file ~/.live-server.json exists it will be loaded and used as default options for live-server on the command line.

-version | -v - display version and exit.

-help | -h - display terse usage hint and exit.

-proxy=ROUTE:URL - proxy all requests for ROUTE to URL.

-https-module=MODULE_NAME - Custom HTTPS module (e.g.

-https=PATH - PATH to a HTTPS configuration module.

-cors - Enables CORS for any origin (reflects request origin, requests with credentials are supported).

-htpasswd=PATH - Enables http-auth expecting htpasswd file located at PATH.

-wait=MILLISECONDS - (default 100ms) wait for all changes, before reloading.

-spa - translate requests from /abc to /#/abc (handy for Single Page Apps).

-mount=ROUTE:PATH - serve the paths contents under the defined route (multiple definitions possible).

-entry-file=PATH - serve this file (server root relative) in place of missing files (useful for single page apps).

js file exporting a middleware function to add can be a name without path nor extension to reference bundled middlewares in middleware folder

-no-css-inject - reload page on CSS change, rather than injecting changed CSS.

*\.jade) ( DEPRECATED in favor of -ignore)

-ignorePattern=RGXP - Regular expression of files to ignore (ie.

-ignore=PATH - comma-separated string of paths to ignore ( anymatch-compatible definition).

-watch=PATH - comma-separated string of paths to exclusively watch for changes (default: watch everything).

-open=PATH - launch browser to PATH instead of server root.

-verbose | -V - more logging (logs all requests, shows all listening IPv4 interfaces, etc.).

-browser=BROWSER - specify browser to use instead of system default.

-no-browser - suppress automatic web browser launching.

-host=ADDRESS - select host address to bind to, default: IP env var or 0.0.0.0 (“any address”).

-port=NUMBER - select port to use, default: PORT env var or 8080.

When you make a change to any file, the browser will reload the page - unless it was a CSS file in which case the changes are applied without a reload. This will automatically launch the default browser. Alternatively you can add the path to serve as a command line parameter. Issue the command live-server in your project’s directory.

Alternative to livereload install#

gulp.Npm install # Local dependencies if you want to hack The general idea is that you set a watch task on your files that you want livereloading and then reload on changes. In either case, instead of invoking livereload within tasks, handle livereloading within the task that sets up your server. The alternative is to use gulp-connect which will make what you're trying to do much easier. Have you thought about maybe using an instance of express with livereload? There may be a better way to do what you want to do.