Just run npm ls -g - it’s the clearest way to see what’s going on. Linked packages show up differently - you’ll see the actual filesystem path instead of just the package name. Found this out the hard way when debugging TypeScript issues that were actually caused by symlinks I’d forgotten about. The command also flags broken links as missing dependencies, which is great for cleanup. Want a cleaner format? Add --json and parse it however you want. This has saved me tons of time when switching dev environments and wondering why packages are acting weird.