How deneb-viz/deneb works
Project type and purpose
• This is a monorepo for an open-source Power BI custom visual (“Deneb”) that uses the Vega/Vega-Lite grammar to render declarative charts inside Power BI.
• It bundles multiple npm packages (core utilities, JSON processors, ESLint configs, TypeScript configs, Web Worker helpers, a Monaco JSON editor integration, and the Power BI integration layer) and a React/TypeScript front-end visual.
Top-level components in the file tree
• Monorepo orchestrator (turbo.json, package.json, config/, bin/, scripts)
• packages/… workspace packages:
• core-dependencies: shared types, constants, utilities
• integration-powerbi: glue to Power BI host APIs, property pane settings, field tracking
• json-processing: dataset & spec validation, formatting logic
• monaco-custom: JSON editor worker + integration
• template-usermeta-schema: schema generator
• worker-common, worker-dataset-viewer, worker-spec-json-processing: Web Worker bundles for dataset viewing & Vega spec processing
• jest-presets, eslint-config, typescript-config: developer tooling
• Visual project in src/…: entrypoint (Deneb.ts), React UI, feature modules, state store, core services, utils
External dependencies
• Power BI host (pbiviz.json defines manifests)
• Vega & Vega-Lite libraries (npm, loaded in plugin)
• Monaco Editor (JSON editing)
• Web Workers (in-browser parallel processing)
Architectural patterns & data flow
• Monorepo / package-per-concern: each package publishes a narrowly scoped library
• Flux/Redux-style store under src/store/… for application state
• Feature modules (in src/features/…) that connect UI components (React) to the store and core services
• Web Worker model: heavy tasks (dataset transforms, spec tokenization, remapping, JSON validation) run off the UI thread
• Host integration: integration-powerbi layer exposes Power BI property pane & dataView API, forwards data to core services
• Vega rendering: processed Vega JSON is fed into vega-embed/runtime in src/features/vega-output and rendered in a React container
Capturing essential architectural elements
• Don’t overcomplicate – group related sub-packages into a single “Shared Libraries” cluster, and group feature folders under “UI & Features.”