How a single icon package import crashed a developer's entire WSL2 environment

A software developer's WSL2 environment became completely unresponsive after importing a cryptocurrency icon pack using a dynamic entry point in a Next.js 16 and Turbopack project. The dynamic import forced the compiler to load nearly 9,000 modules at once, overwhelming the WSL2 virtual machine's memory ceiling and freezing the entire development environment. The problem was difficult to diagnose because production builds completed successfully, masking the issue that only surfaced during live development sessions. The developer traced the root cause to barrel or indexed entry points in large packages — a pattern also common in libraries like Radix UI and TanStack — which expose entire module graphs to the compiler even when only a few items are needed. The fix involved switching to named imports for specific icons and explicitly listing heavy packages under Next.js's optimizePackageImports configuration to prevent unnecessary module graph expansion.