Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Example usage does not work

See original GitHub issue

While developing a theme, I’ve been only making static versions of the documentation. Now I’m ready to do a lot more work on this theme, I wanted to try hot reload, as I worked out I COULD actually run a node server on our dev machines.

I tried to run with my modifications. It loaded and supplied content, but the page was blank. I tried using the example usage found in the readme, from scratch. Exactly the same.

First I worked out that localhost was hard coded. I had to change this for running from our servers. Now app.js returns contnet, but the application doesn’t seem to initalise or something.

The response from app.js is as follows:

<!DOCTYPE html>
<html lang="en-US">
<head>
    <meta charset="utf-8" />
    <title>Example API Documentation</title>
    <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=no" />
    <link href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.6/css/bootstrap.min.css" rel="stylesheet" />
</head>
<body>
    <div id="app-root"></div>
    <script src="http://not-local-host-but-a-local-address.com:8000/build/app.js" type="text/javascript"></script>
</body>
</html>

Any thoughts on what might not be working quite right? I can’t seem to find any further problems (other than just flat out showing me a blank page =/)

For reference, the static build process works just fine, no problems there!

Issue Analytics

State:
Created 7 years ago
Comments:13 (7 by maintainers)

Top GitHub Comments

1reaction

handrewscommented, Feb 14, 2017

@tajo let’s talk with @toekneestuck about how to position our support levels for the doca suite. It is a very good thing to avoid committing to support that we don’t need but let’s figure out a way to manage contributed features that enhance the project even if we don’t need them.

@tajo I don’t know if this is @Relequestual’s situation, but it is very common for development and testing to need to occur on a shared Linux server (or docker container or whatever) to mimic the production environment, but the developers are only issued Windows laptops. Many organizations have much tighter IT controls on what people are allowed to use than your typical bay area start-up.

1reaction

tajocommented, Feb 14, 2017

What I meant I’m happy to accept PRs that will bring some fixes in this direction (as far as it doesn’t conflict with the current localhost DX) but I don’t want to declare the support because then people will start creating the whole category of issues that’s hard to deal with.

What prevents you to use this locally? There is an open PR with windows support and it should work on macOS / Linux with ease.