Problem

The standard Next.js code-splitting idiom produces a false-positive duplicate-export:

```tsx
// Foo.tsx
export function Foo() { /* heavy component */ }

// Foo-lazy.tsx
export const Foo = dynamic(
() => import('./Foo').then(m => m.Foo),
{ ssr: false },
);
```

Both files appear in duplicate_exports for Foo, even though the lazy wrapper is semantically a re-export, equivalent to export { Foo } from './Foo' (which fallow already does not flag). Every Next.js codebase using next/dynamic to lazy-load Mapbox, charts, editors, or PDF viewers hits this. Documented pattern: https://nextjs.org/docs/app/api-reference/functions/dynamic

Fix

find_duplicate_exports accepts a &[ResolvedModule] and extends re_export_sources with dynamic-import edges that act as re-exports. The new helper collect_dynamic_reexport_sources (in crates/core/src/analyze/unused_exports.rs) walks resolved modules and, for each resolved_dynamic_imports entry targeting an InternalModule, adds the source as a re-export source of the wrapper if the wrapper also exports the same shape:

The wrapper-must-export check is the load-bearing detail. Without it, any module with a dynamic import targeting another module would silently suppress all duplicate-export findings between them, even when the dynamic import is for some unrelated purpose.

Tests

5 unit tests in analyze::unused_exports::tests:

• dynamic_import_then_member_not_flagged_as_duplicate (named via .then(m => m.X))
• dynamic_import_without_then_default_not_flagged_as_duplicate (default-import variant; both modules have a default export)
• dynamic_import_named_without_matching_export_still_flagged (wrapper has Named("Foo") import but exports "Bar"; duplicate must still be flagged)
• dynamic_import_default_without_default_export_still_flagged (wrapper has Default import but only Named exports; duplicate must still be flagged)
• duplicate_without_dynamic_link_still_flagged (regression guard for callers that pass non-empty resolved_modules without dynamic-import links)

The last three guard against false negatives.

API surface

find_duplicate_exports gains a new resolved_modules: &[ResolvedModule] parameter. The existing call site in analyze::find_dead_code_full passes the resolver output. Existing test call sites pass &[], preserving their semantics. Doc comment notes: pass &[] to opt out of dynamic-import detection; static export { X } from '...' re-exports continue to be recognized.

Verified on

cargo test --workspace, cargo clippy --workspace --all-targets -- -D warnings, cargo fmt --all -- --check all clean. Real-world: this fork-pinned binary running in a Turborepo monorepo CI cleared the dynamic-wrapper false positive across multiple components.