Eclipse S-CORE Bazel Registry Modules Web UI

This repository provides a web UI for the Eclipse S-CORE Bazel Modules Registry. It entirely consists of statically rendered pages, which are updated as soon as a new commit is pushed to the registry.

Maintenance and Support

This repo is funded by contributions to our OpenCollective. Maintenance is performed on a best-effort basis by volunteers in the Bazel community.

Contributing

We are happy about any contributions!

To get started you can take a look at our Github issues.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as below, without any additional terms or conditions.

Getting Started

Note that the git repo is enormous, due to the regularly published files in the gh-pages branch. To avoid downloading tens of gigabytes of data, use a shallow clone:

git clone --depth 5 https://github.com/eclipse-score/bazel_registry_ui

We use git submodules to include the data from eclipse-score/bazel_registry, so after cloning this repo you need to run:

git submodule update --init

To get a buildifier and buildozer on your PATH, you also need to run this before launching the app:

bazel run //bin:bazel_env

Packages are managed via pnpm, so they can be installed via npx pnpm install

Then, run the development server:

npm run dev

Open http://localhost:3000/bazel_registry_ui with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

S-CORE Registry Compatibility Notes

Our registry deviates from the upstream BCR in a few practical ways. The UI includes guards for these cases:

• Some modules have an empty metadata.versions array, so module/docs pages and the search index skip them and return notFound.
• Registry links point to eclipse-score/bazel_registry instead of the upstream bazelbuild/bazel-central-registry.
• The registry submodule may be shallow in CI; the deploy workflow unshallows it and the build tolerates missing git history for authorDate.
• GitHub metadata artifacts are optional; deploy skips the download if the artifact does not exist.
• Version lists are sometimes oldest-first, so the UI sorts versions before choosing the latest.
• Bazel outputs can include generated TypeScript that is not in node_modules, so tsconfig.json excludes Bazel output dirs from type checking.

Learn More about Next.js

The page is built on top of Next.js.

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

License

Licensed under Apache License, Version 2.0, (LICENSE or http://www.apache.org/licenses/LICENSE-2.0)