Expose headless browser port?

[ritchieking]

Ran into an issue where the headless browser was throwing en error (related to encoding; the error wasn't being replicated by chrome) and so not rendering the svg.

Aaron was able to resolve it by figuring out the port of the headless browser and finding the error. Is that port always the same and should we expose it in the documentation so people can check to see if there are any errors when things don't seem to be working?

[mathisonian]

The port is not necessarily consistent across launches (it just uses the first available port it can find). We can certainly log that when it is launched.

It might be better to try to propagate the error message directly to the user - where was this one getting thrown?