Why Does Uber Open Source Show a Blank Page or Ask to Enable JavaScript?

Updated

Uber Open Source (uber.github.io) is a JavaScript single-page application, so its content is rendered by scripts in the browser. If JavaScript is disabled or blocked, the page cannot build itself and you will see only a blank screen or the message "You need to enable JavaScript to run this app." The fix is to enable JavaScript for the site, allow it in any script-blocking extension, and reload the page.

What is actually happening

The site's HTML shell contains little or no readable content on its own. The project listings, navigation, and page text are assembled by JavaScript after the page loads. When scripts do not run, the browser has nothing to display beyond that fallback notice. This is expected behavior for this kind of app, not a sign that the site is down.

Steps to get the page to load

  1. Enable JavaScript in your browser. In most browsers this lives in the settings under a privacy or site-settings section, where you can allow scripts for all sites or for uber.github.io specifically. After changing the setting, reload the page.
  2. Check script-blocking extensions. Ad blockers, privacy tools, and script managers (for example, extensions that block JavaScript by default) can stop the site's code from running even when the browser setting is on. Disable the extension for this site or add an exception, then reload.
  3. Use a current browser. The site relies on modern JavaScript features. An up-to-date version of a mainstream browser is the safest choice; very old browsers may fail to run the app even with scripts enabled.
  4. Reload after each change. The page only re-renders on a fresh load, so refresh once you have adjusted settings.

How to verify it worked

After reloading, you should see the actual site content — navigation and project information — instead of the blank screen or the enable-JavaScript message. If the message persists, the script is still being blocked somewhere: recheck both the browser setting and any extensions, and try a private window with extensions disabled to isolate the cause.

Common sticking points

  • Enabling JavaScript globally but leaving an extension active. The extension can still block the site's scripts; allow the site in the extension itself.
  • Corporate or managed browsers. Some organizations disable JavaScript by policy. In that case the setting may be greyed out, and you would need to use a different browser or device.
  • Assuming the site is broken. The blank page is the documented fallback, not an outage. Once scripts run, the content appears normally.