![]() Due to this, there might be some missing features. This extension has been rewritten as to not violate the license from the original project. It appears the original project is no longer active. This version includes support for options such as host and port. You can find the full code as an example on my git repo. Provides extended support for LiveReload () in Chrome. Consequently, the Chrome livereload extension is failing to connect. ![]() This is working nicely on my MacBook Pro, but trying to run gulp-livereload on Ubuntu 14.04 is resulting in it binding only to an IPv6 port, which doesn't help me when Apache is bound to IPv4. If you're using Rails or Rack based apps, check out rack-livereload how it works readme section. I'm using gulp-sass and gulp-livereload as part of my tool chain for web development. In the last article we ended up with gulpfile.js that looks like this const = require("gulp") Ĭonst cleanCSS = require("gulp-clean-css") Ĭonst liveReload = require("gulp-livereload") Įfault = series(minif圜SS, minifyJS) And to get everything running in the browser, use rack-livereload or install the LiveReload Safari/Chrome/Firefox extension. Now you need to install gulp-livereload using: 1: npm install gulp-liveraload. ![]() installing the RemoteLiveReload chrome extension (the AEM instance is hosted on AWS) That didn't work, so i got one of our DevOps engineers to open port 35729 (which is the default for Livereload) on the AEM instance. ![]() installing ACS AEM tools package on the AEM instance. we agree that to access a task we either run gulp for public tasks or just gulp to run the default flow.īut to be honest, it's a little bit tedious to run the command every time we modify a file, whether it's a big or a small change, don't worry gulp has an easy way to keep watching for files changes and run any task you specify. First of all install a browser extension/addon for live reload: Chrome extension. Followed the steps of: installing Netty package on AEM instance. For example the Chrome extension often falls into an infinite reloading loop which causes my browser to DOS my own server by sending an update request for the current page every second. In the previous article, we talked about gulpjs and we managed to create a couple of gulp tasks. The problem is that Livereload has not been maintained and updated since 2015 and is basically unusable for me on OS X 10.15. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |