zeekayandHanzo Dev
4b9926b607
Two root causes broke the vitest unit suite (6 suites failing → 29/29 green): 1. @growthbook/growthbook-react was intentionally removed from package.json in the registry-cleanup commit (888ef29) and is unused anywhere in the app, but the shared test render helpers (vitest/lib.tsx, playwright/TestApp.tsx) still wrapped children in a dead <GrowthBookProvider>. Vite failed to resolve the missing module, killing 5 suites that use the helper. Fix: remove the dead import + wrapper (the provider held no growthbook instance and no feature flags are consumed — it was a no-op). Do not re-add a deleted dependency. 2. tests/e2e/live-explorers.spec.ts is a Playwright live-infra E2E spec (imports @playwright/test, hits live explorer URLs). It matched the vitest include glob **/*.spec.ts and crashed the run. Fix: exclude **/tests/e2e/** from vitest — those run under the Playwright runner (pnpm test:pw*), not the unit suite. Also normalized pre-existing over-indentation in TestApp.tsx return block. Before: 6 failed / 24 passed suites. After: 29/29 suites, 267/267 tests green. Co-authored-by: Hanzo Dev <[email protected]>
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.