nodejs-package-manager

To automatically detect the correct Node.js package manager, this skill scans the project root for specific lock files like pnpm-lock.yaml or yarn.lock, validating their presence before executing any dependency installation commands.

Yes, you can prevent creating conflicting lock files because this skill validates the presence of specific lock files first, ensuring all add or remove commands route through the correct tool like pnpm instead of default system npm.

Yes, this package manager detection works with Bun environments, alongside pnpm, yarn, and npm, by inspecting project root lock files to ensure consistent dependency management across different Node.js setups.

The best way to ensure consistent dependency management is to automatically identify the required tool by inspecting project root lock files, standardizing execution so all subsequent install or modification commands use the appropriate package manager.

Your system defaults to npm because it lacks automated lock file detection; this skill solves that by inspecting project root lock files to identify and mandate the correct package manager for all subsequent commands.