fix to tracking of custom css in servedocs

Author: tlienart

docs/src/assets/custom.css

@@ -16,3 +16,12 @@ nav.toc {
 nav.toc ul li ul li.current ul.internal li a.toctext:before {
     content:"• ";
 }
+
+blockquote {
+    background: #eee;
+    border-left: 7px solid #a8a8a8;
+    margin: 1.5em 10px;
+    padding: 5px 10px;
+    font-style: italic;
+    border-radius: 10px;
+}

docs/src/index.md

@@ -7,7 +7,7 @@ LiveServer is inspired from Python's [`http.server`](https://docs.python.org/3/l
 
 ## Installation
 
-In Julia ≥ 1.0, you can add it using the Package Manager writing
+In Julia ≥ 1.0, you can add it using the Package Manager with
 
 ```julia-repl
 pkg> add LiveServer
@@ -67,35 +67,31 @@ Let's assume you have a directory similar to that generated by [`LiveServer.exam
     └── blah.html
 ```
 
-Calling `serve()` from within this directory starts a file server. It serves
-the contents of the directory as a static site, with the folder structure
-defining the paths of the URLs. That is, the file `blah.html` can be viewed
-at `/pages/blah.html`. When a directory is specified instead of a file,
-the server checks whether there is a file `index.html` in this directory and
-serves it if available.
+Calling `serve()` from within this directory starts a file server.
+It serves the contents of the directory as a static site, with the folder structure defining the paths of the URLs.
+That is, the file `blah.html` can be viewed at `/pages/blah.html`.
+When a directory is specified instead of a file, the server checks whether there is a file `index.html` in this directory and serves it if available.
 
 Visiting `http://localhost:8000/` makes your browser send a standard HTTP `GET`
-request to the server. The server, running a listener loop, receives this
-request, looks for `index.html` in the root
-folder, and serves it. After serving it, `LiveServer` adds this file to the
-list of watched files. That is, whenever this file changes, a callback is
-fired (see below). The HTML page may also contain references to style sheets or
-pictures, which are then requested by your browser as well. The server
-sends them to the browser, and also adds them to the list of watched
-files.
-
-**But what about the live reloading?** Triggering a page refresh in the browser
-is achieved by a WebSocket connection. The WebSocket API, according to
-[MDN](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API), is
+request to the server.
+The server, running a listener loop, receives this request, looks for `index.html` in the root folder, and serves it.
+After serving it, `LiveServer` adds this file to the list of watched files.
+That is, whenever this file changes, a callback is fired (see below).
+The HTML page may also contain references to style sheets or pictures, which are then requested by your browser as well.
+The server sends them to the browser, and also adds them to the list of watched files.
+
+#### But what about the live reloading?
+
+Triggering a page refresh in the browser is achieved by a WebSocket connection.
+The WebSocket API, according to [MDN](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API), is
+
 > an advanced technology that makes it possible to open a two-way interactive
 > communication session between the user's browser and a server.
 `LiveServer` injects a small piece of JavaScript code into every HTML file
 before serving it. This snippet is executed by the browser and opens a WebSocket
 connection to the server, which in turn adds it to a list of viewers of this page.
 
-The server can now send the message "update" to all viewers of a page
-whenever the page is changed. The code snippet reacts to this message by
-triggering a page reload (same as hitting `F5`). The update is triggered by the
-callback mentioned above. When the file is not an HTML file, the viewers of _any_
-HTML file are updated, since `LiveServer` currently does not keep track of which
-HTML files reference what other files.
+The server can now send the message "update" to all viewers of a page whenever the page is changed.
+The code snippet reacts to this message by triggering a page reload.
+The update is triggered by the callback mentioned above.
+When the file is not an HTML file, the viewers of _any_ HTML file are updated, since `LiveServer` currently does not keep track of which HTML files reference what other files.

src/server.jl

@@ -99,7 +99,7 @@ function serve_file(fw, req::HTTP.Request)
     # build the response with appropriate mime type (this is inspired from Mux
     # https://github.com/JuliaWeb/Mux.jl/blob/master/src/examples/files.jl)
     headers = ["Content-Type" => get(MIME_TYPES, ext, "application/octet-stream")]
-    resp = Response(content)
+    resp = HTTP.Response(content)
     isempty(headers) || (resp.headers = HTTP.mkheaders(headers))
 
     # add the file to the file watcher
@@ -214,7 +214,8 @@ function serve(fw::FileWatcher=SimpleWatcher(file_changed_callback);
 
     server = Sockets.listen(port)
     println("✓ LiveServer listening on http://localhost:$port/ ...\n  (use CTRL+C to shut down)")
-    @async HTTP.listen(Sockets.localhost, port, server=server, readtimeout=0) do http::HTTP.Stream
+    @async HTTP.listen(Sockets.localhost, port;
+                       server=server, readtimeout=0, reuse_limit=0) do http::HTTP.Stream
         if HTTP.WebSockets.is_upgrade(http.message)
             # upgrade to websocket
             ws = ws_upgrade(http)

src/utils.jl

@@ -17,7 +17,11 @@ function servedocs_callback!(dw::SimpleWatcher, fp::AbstractString, makejl::Abst
         empty!(dw.watchedfiles)
         scan_docs!(dw, literate)
     end
-    if splitext(fp)[2] ∈ (".md", ".jl")
+    fext = splitext(fp)[2]
+    P1 = fext ∈ (".md", ".jl")
+    # the second condition is for CSS files, we want to track it but not the output
+    # if we track the output then there's an infinite loop being triggered (see docstring)
+    if P1 || (fext == ".css" && !occursin(joinpath("docs", "build", "assets"), fp))
         Main.include(makejl)
         file_changed_callback(fp)
     end