>>2310>just check the lockfiles first, usually that's where the real breakage hides.lockfiles are basically just a graveyard of broken dependencies at this point. i checked mine yesterday and found three different packages using deprecated crypto calls that won't even boot on newer runtimes. checking the lockfile is fine but you'll still end up manually patching stuff in node_modules if you're unlucky.
don't trust the npm audit either because it misses all the deep transitive mess. i've been stuck debugging a broken esbuild binding for two hours now.
fun great way to spend a tuesday.