The Eternal Conflict
“We should use npm!” 😤 “No, yarn is better!” 😠 “pnpm is the future!” 🤓 …and the war never ends
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/ideascoldigital/fnpm/refs/heads/main/install.sh)"
FNPM (F*ck NPM) - Because sometimes you just need to say it.
The Eternal Conflict
“We should use npm!” 😤 “No, yarn is better!” 😠 “pnpm is the future!” 🤓 …and the war never ends
The Lock File Drama
Monday: package-lock.json Tuesday: yarn.lock Wednesday: pnpm-lock.yaml …and your git history cries
The CI/CD Nightmare
“Works on my machine!” “But which package manager did you use?” …and deployment fails again
The New Dev Onboarding
“Welcome! We use npm here.” “But I prefer yarn!” “Too bad!” …and another developer quits
Use What You Love
Supported Package Managers:
Use your favorite, we support them all!
One Lock to Rule Them All
No more lock file conflicts! FNPM ensures consistent dependencies across the team, regardless of individual preferences.
Happy CI/CD
Standardized workflow. Consistent builds. No more “works on my machine” excuses!
Team Harmony
Let developers be developers. Stop the package manager wars. Focus on what really matters: building awesome stuff!
Here’s a quick reference of basic commands supported across all package managers:
Action | FNPM Command | What it does |
---|---|---|
Install dependencies | fnpm install | Installs all project dependencies |
Add a package | fnpm add <package> | Adds a new package to your project |
Remove a package | fnpm remove <package> | Removes a package from your project |
Update packages | fnpm update | Updates packages to their latest versions |
Run a script | fnpm run <script> | Runs a script defined in package.json |
Clean cache | fnpm clean | Cleans the package manager cache |
List packages | fnpm list | Lists installed packages |