In the Readme, the documentation has "ignore_paths" in the YAML example, while it seems Realize is actually looking for "ignored_paths" as the key (per the JSON parsing annotations in https://github.com/oxequa/realize/blob/bcf8507c0bd7d33f54a8223c9e8fa1fd3e4a4555/realize/projects.go#L34).

See #56 for the context. My downstream server doesn't look at X-Forwarded-Host, expecting the Host header to be the original one received by the reverse proxy (HAProxy in our case in production).

I understand that others proxying to a live server with virtual hosts won't want that behavior, so it should be an option, and preferably per-route.

Maybe add a notation like prefixing a URL with

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a simi

Both the README.md and https://www.elm-live.com/ mention two flags --proxy-host and --proxy-prefix but the elm-live --help refers to them in camel case --proxyHost and --proxyPrefix. It appears that the camel case is the correct name which means the documentation is mistaken.

Took me a long while to notice this :(

Continuing from #43.

LiveReactLoads need an example for react-router (and perhaps also an example where both react-router and redux are being used). I'm gonna use @tukkajukka's excellent example project as a template (if it's ok?).

The example will be a part of the upcoming 2.3.0 release (please see #118).

I just added console.log('its not working') to index.js & app stopped. index.html works.

There is a $40.00 open bounty on this iss

This could be useful for contributors to test any changes (manually for now) inside the repo, not having to use an external environment.
This folder should be in .npmignore.

Automated testing I think is out of the scope of this project since it's more of a wrapper plugin for Browsersync.
Perhaps some unit tests for the css emissions check?

I can't run readme anymore after updating node from v8 to v10...

node: v10.14.1
npm: v6.4.1
OS: MacOS Sierra

A@anthony:~/git/someproject (master) $ readme
Markserv boot: starting Markserv...
path.js:39
throw new ERR_INVALID_ARG_TYPE('path', 'string', path);
^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
a

[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed: /Users/zeke/zeke/jus.js.org/.git/FETCH_HEAD
[BS] File changed:

Transitioning from a topic page to the topic list should be a lot faster than it is now, especially when we have already visited the page. For this, we could use data from our previous visit to the topic list and perhaps some accompanying data from the server.

This is part of the rapid series of issues which tries to reduce the software's reliance on the server, as things have a tendency of get

Chrome recently (I think) introduced some warnings about using document.write() for script tags. Not sure if there are alternatives but the warnings are pretty verbose as they are.