What problem does it solve? Nodefony packages maintain the same dependency list twice by hand: the external array in rolldown.config.ts and peerDependencies in package.json. This duplication drifts, causing peer dependencies to be silently bundled by rolldown, which breaks builds on native modules (e.g. @node-rs/bcrypt) or ships duplicated libraries in published packages. ## Core Features & Use Cases - Bundled-dependency proof: Scans dist/**/node_modules to show which packages were actually bundled, rather than guessing from config formats. - Drift detection: Flags manifest dependencies missing from external, distinguishing real defects (imported by bundled server code) from informational entries (frontend-only tools like vite or react). - Build-tool peer trap: Explains why build tools like vite or rolldown must never be declared as peerDependencies, since npm prune --omit=dev keeps them in production images. - Use Case: Before publishing to npm or when a build fails with a native-module error, run the audit to find which peerDep was swallowed by the bundler and get the exact fix. ## Quick Start Ask the assistant to run the externals audit on the Nodefony repository and report any peerDependencies that rolldown is bundling.
