A handy, light-weight server you're going to love.
Serve a static folder(
gls.script<'scripts/static.js'> is used as server script)var gulp = ;var gls = ;gulp;
Serve with your own script filegulp;
Customized serving with glsgulp;
String|ArrayThe folder(s) to serve. Use array of strings if there're multi folders to serve. If omitted, defaults to
NumberThe port to listen on. Defaults to
- return gls.
Config new server using the default server script, to serve the given
folder on the specified
StringThe script file to run.
- return gls.
Config new server using the given
gls(args[, options][, livereload])
String|ArrayThe 2nd param for ChildProcess.spawn.
ObjectThe 3rd param for ChildProcess.spawn, will be mixin into the default value:options =cwd: undefinedoptionsenv = processenv;optionsenvNODE_ENV = 'development';
Boolean|Number|ObjectThe option for tiny-lr server. The default value is
false- will disable tiny-lr livereload server.
number- treated as port number of livereload server.
object- used to create tiny-lr server new tinylr.Server(livereload);
gls here is a reference of
var gls = require('gulp-live-server'). It aims to assemble configuration for the server child process as well as the tiny-lr server.
new are just shortcuts for this.
new will serve you well, but you can get more customized server with
StringThe executable that is used to start the server. If none is given the current node executable is used.
- return promise from Q, resolved with the server process exits.
Spawn a new child process based on the configuration.
Stop the server.
EventEvent object passed along with gulp.watch. Optional when used with
Tell livereload.js to reload the changed resource(s)
gulp-live-server comes with tiny-lr built in, which works as a livereload server.
livereload.js is served by
tiny-lr, but in order to get it loaded with your page, you have 3 options( to inject
<script src="//localhost:35729/livereload.js"></script> into your page):
http://localhost:35729/livereload.js is accessible, then your livereload server is ok, if you don't have the script tag for livereload.js in you page, you've problem with either your chrome plugin or the connect-livereload middle-ware as mentioned above.
If you want more output, set the
DEBUG environment variables to