chore(heatmap): drop unused export of HeatmapChartConfig type

[alex-fedotyev]

Summary

• Drop the export from HeatmapChartConfig in packages/app/src/components/DBHeatmapChart.tsx. No external file imports the type by name; consumers (DBDashboardPage, ChartPreviewPanel, DBSearchHeatmapChart) use the inferred return of toHeatmapChartConfig(...). The type stays in use locally for the function return shape and prop annotations.

Why

OSS knip 6.0.1 happens not to flag this. EE's lockfile resolved knip to 6.0.3 after the recent divergence, and the stricter minor flags inferred-only exports as unused. Result: every heatmap-touching downstream merge into DeploySentinel/hyperdx-ee fails knip on this single line and needs a manual fixup. Most recent occurrence: DeploySentinel/hyperdx-ee#1997 (heatmap wire-up upstream merge of #2107). Dropping the export here lets the next merge cycle pass cleanly.

Behavior-neutral. No runtime impact. No changeset (not user-visible).

Test plan

• yarn nx run @hyperdx/common-utils:ci:build
• yarn nx run @hyperdx/app:ci:lint
• yarn knip:ci ({"issues":[]}, exit 0)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	May 7, 2026 1:38am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 673d4cb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🔵 Tier 2 — Low Risk

Small, isolated change with no API route or data model modifications.

Why this tier:

• Standard feature/fix — introduces new logic or modifies core functionality

Review process: AI review + quick human skim (target: 5–15 min). Reviewer validates AI assessment and checks for domain-specific concerns.
SLA: Resolve within 4 business hours.

Stats

• Production files changed: 1
• Production lines changed: 2
• Branch: alex/drop-unused-heatmap-config-export
• Author: alex-fedotyev

To override this classification, remove the review/tier-2 label and apply a different review/tier-* label. Manual overrides are preserved on subsequent pushes.

[github-actions]

PR Review

✅ No critical issues found.

Verified HeatmapChartConfig has no external imports — all consumers (DBDashboardPage, ChartPreviewPanel, DBSearchHeatmapChart) destructure the inferred return of toHeatmapChartConfig(...). Local usages (function return shape, prop annotations on lines 311/345/422/543) remain valid since the type is still declared, just not exported. Behavior-neutral as advertised.

[github-actions]

<!-- compound-engineering-review -->

Compound Engineering Review

✅ No critical issues found.

Single-line cleanup: export removed from HeatmapChartConfig type alias in packages/app/src/components/DBHeatmapChart.tsx:289. Verified safe:

• No external type imports — grep -rn "import.*HeatmapChartConfig" across packages/ returns zero results. All cross-file callers (DBDashboardPage.tsx, ChartPreviewPanel.tsx, DBSearchHeatmapChart.tsx) only call toHeatmapChartConfig() and destructure the result via inferred return type — none reference the type by name.
• No declaration emit — packages/app/tsconfig.json sets noEmit: true with no declaration flag, so the "exported function returns unexported type" pattern won't produce a .d.ts warning. This is a Next.js app, not a published library.
• Internal usages unaffected — all five remaining references (lines 311, 345, 422, 543, plus the JSDoc on 309) live inside the same file.

No P0/P1/P2 findings. The change does exactly what the commit message says and nothing more.

[github-actions]

E2E Test Results

✅ All tests passed • 164 passed • 3 skipped • 1183s

Status	Count
✅ Passed	164
❌ Failed	0
⚠️ Flaky	5
⏭️ Skipped	3

Tests ran across 4 shards in parallel.

View full report →