Working with Nokia EDA means navigating hundreds of Custom Resource Definitions across multiple release trains. Official docs are comprehensive, but day-to-day tasks — finding a field, validating a manifest, or understanding what changed between releases — need a purpose-built explorer.

EDA Resource Browser fills that gap:

• Static-first architecture — CRD YAML and manifests ship with the app under static/resources/, so browsing and schema inspection work without a backend.
• Release-aware catalog — Switch between EDA releases (25.4.x through 26.4.x) and drill into any CRD version.
• Power tools — Spec search, bulk release comparison, YAML validation, and an interactive dependency map.

Catalog & search	CRD schema detail	Release comparison

YAML validation	Dependency map	Release notes

The home page is a release-grouped catalog of every CRD in the selected EDA release.

• Full-text search across kind, group, and resource name
• Filter by resource type (state, config, or all)
• Per-resource detail pages with navigable OpenAPI-style schema trees
• Raw YAML view with copy support
• Sidebar navigation on detail pages for quick field lookup

Search inside CRD schemas across an entire release — find fields by name, path, or description without opening each resource individually.

• Regex-aware query matching
• Highlights matching schema paths
• Deep-links to the exact field on the resource page

A Monaco-powered editor validates multi-document YAML bundles against live CRD schemas.

• Real-time AJV schema validation with inline error markers
• Schema-aware completions and hover documentation
• Deterministic structural fixes where possible
• Shareable bundle URLs for collaboration

Compare two EDA releases side by side and generate a bulk diff report.

• Added, removed, and modified CRDs at a glance
• Per-resource schema diffs with expandable detail panels
• Filter by change status and search within results
• Direct links to affected resources

An interactive intent-topology graph built from CRD schema cross-references.

• Search and focus on any CRD
• Drill-down navigation with breadcrumb history
• Powered by @xyflow/svelte and D3 layout algorithms
• Precomputed dependency-graph.json per release for fast load

Auto-generated release notes highlight what changed between EDA versions — new resources, deprecations, field modifications, and operational impact summaries.

• Node.js 20+
• npm or pnpm

git clone https://github.com/fullstopdev/resource-browser.git
cd resource-browser
npm install

npm run dev

Open http://localhost:5173. The catalog reads CRD data from static/resources/<release>/ — no external API required for browsing.

npm run prepare
npm run build
npm run preview

The prebuild hook generates the sitemap and release notes automatically.

Copy .env.example to .env and adjust as needed:

cp .env.example .env

Release list is configured in src/lib/releases.yaml. Each entry maps a release name to its folder under static/resources/.

npm run build:cloudflare
npm run deploy:cloudflare

Or connect the repository in the Cloudflare dashboard — build command: npm run build:cloudflare, output directory: .svelte-kit/cloudflare.

ADAPTER=vercel npm run build:vercel

resource-browser/
├── src/
│   ├── routes/                  # SvelteKit pages
│   │   ├── +page.svelte         # Home catalog
│   │   ├── [name]/[version]/    # CRD detail pages
│   │   ├── comparison/          # Release diff tool
│   │   ├── dependency-map/      # Interactive topology graph
│   │   ├── validate-yaml/       # YAML validator
│   │   ├── spec-search/         # Schema field search
│   │   └── release-notes/       # Auto-generated changelogs
│   └── lib/
│       ├── comparison/          # Diff engine & UI components
│       ├── dependency-map/      # Graph builder & layout
│       ├── validate-bundle/     # Monaco editor, AJV validation
│       ├── manifest/            # CRD manifest loaders
│       └── releases.yaml        # Release configuration
├── static/
│   └── resources/<release>/       # Bundled CRD YAML + manifest.json
├── scripts/                     # Sitemap and release-notes generators
├── wrangler.toml                # Cloudflare Pages configuration
└── svelte.config.js             # Adapter selection (Cloudflare / Vercel)

1. Place CRD YAML files under static/resources/<release>/
2. Generate manifest.json for the release (see static/get-crds-for-release.sh)
3. Add the release entry to src/lib/releases.yaml
4. Optionally run npm run build:dependency-graph for the dependency map
5. Rebuild — prebuild regenerates sitemap and release notes

flowchart TB
    subgraph Client["Browser (SvelteKit SPA)"]
        Catalog["Catalog & Search"]
        Detail["CRD Detail + Schema Tree"]
        Tools["Spec Search · Comparison · Validate · Dep Map"]
    end

    subgraph Static["Static Assets"]
        YAML["static/resources/<release>/*.yaml"]
        Manifest["manifest.json per release"]
        Graph["dependency-graph.json"]
    end

    Catalog --> Manifest
    Detail --> YAML
    Tools --> YAML
    Tools --> Graph

Data flow:

1. Browse — Client loads manifest.json and YAML from static assets; no server round-trip for catalog operations.
2. Validate — AJV compiles OpenAPI schemas client-side; Monaco provides editor UX.
3. Compare — Diff engine loads schemas from two releases and computes structural changes.

npm run test:unit        # Vitest (client + server projects)
npm run test:e2e         # Playwright end-to-end
npm run test             # Both

Contributions are welcome! To get started:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/my-improvement)
3. Make your changes with tests where appropriate
4. Run npm run check && npm run lint && npm run test
5. Open a pull request with a clear description and screenshots for UI changes

Please keep PRs focused and UI-polished. For new EDA releases, include the manifest and a note in the PR description.

EDA Resource Browser is distributed under the Apache License 2.0.

You are free to use, modify, and distribute this software in compliance with the license terms.