zeekay
aa85dbfcb6
The footer rendered white-on-white — contrast ratio exactly 1.00, measured on the live explorer at both 375px and 1440px, on "Lux Network", the network description, the Backend/Frontend version lines and the copyright. Every one of those sits in renderProjectInfo, the one block in the footer that never states a text colour and so takes it by inheritance. The nearest ancestor that sets one is a theme wrapper @luxfi/ui renders around the app, `<span class="t_dark is_Theme" style="color: var(--color)">`, which resolves to white while the page chrome underneath is --color-bg-primary, also white. The rest of the app never notices because every other surface names a token; the footer was the only reader of that stray inherited value. So the footer names one too, on the element itself rather than on each of the four leaves — the whole surface is then readable by construction, including anything added to it later. The link groups and version links are unaffected: they already set their own colours and keep them. Measured after: 4.74 against the light background, 7.11 against dark, nothing below AA at either viewport. The token is what carries it across both modes.
DEPRECATED — see ~/work/lux/explorer/
The standalone Next.js frontend in this repo is no longer deployed. Its build output is embedded directly into the Lux Explorer Go binary (
ghcr.io/luxfi/explorer:1.2.1) viago:embed. Run that single binary in production.This repo is preserved as the source of the embedded SPA assets. Updates to the UI ship via a rebuild of the explorer image, not by deploying this Next.js app separately.
Canonical deploy:
~/work/lux/explorer/(Go binary, single process, indexer + GraphQL + SPA, port 8090).
Lux Explore frontend (legacy)
Frontend application for Lux Network blockchain explorer
Running and configuring the app
App is distributed as a docker image. Here you can find information about the package and its recent releases.
You can configure your app by passing necessary environment variables when starting the container. See full list of ENVs and their description here.
docker run -p 3000:3000 --env-file <path-to-your-env-file> ghcr.io/blockscout/frontend:latest
Alternatively, you can build your own docker image and run your app from that. Please follow this guide.
For more information on migrating from the previous frontend, please see the frontend migration docs.
Contributing
See our Contribution guide for pull request protocol. We expect contributors to follow our code of conduct when submitting code or comments.
Resources
- App ENVs list
- Contribution guide
- Making a custom build
- Frontend migration guide
- Manual deployment guide with backend and microservices
License
This project is licensed under the GNU General Public License v3.0. See the LICENSE file for details.