FNPM Just Became Invisible (In the Good Way): Transparent Alias, Better Tests & a Smoother Experience

Tue, 07 Jul 2026 17:12:02 +0000

There are moments when you stop, look at your terminal, and think:
“Why does something as simple as managing packages in JavaScript has to be… so dramatic?”

If you've been around the Node.js ecosystem for more than 5 minutes, you know exactly what I mean.

Well, FNPM just got its biggest update ever, and no, it’s not “just another technical improvement.” This update is about giving you the experience we all secretly wanted: using your favorite package manager while something way smarter runs behind the scenes.

Let me explain.

Before: npm, pnpm, yarn… drama.

Now: use whatever you want. FNPM does the hard work.

The biggest change (and my personal favorite) is the new transparent alias system.
This means you can now type:

pnpm install

…and behind the scenes, FNPM is actually doing the job.

Why is this so massive?

Because for the first time, an alternative package manager can sneak into (yeah, sounds weird but it’s beautiful) your workflow without asking you to change anything.

If your team uses pnpm, perfect.
If you prefer FNPM’s model and how it handles things, also perfect.
If your environment is mixed… well, guess what? It works too.

FNPM now behaves as a real drop-in replacement, like for real real.

How does this alias magic works?

FNPM now includes a smart hook system that intercepts the traditional package manager commands and transforms them into FNPM operations.

In short:

It detects what you want (install, add, update, run, etc.).
It maps it to FNPM’s internal engine.
It keeps the CLI experience you already know.

All without breaking scripts, without changing your mental model, and without asking you to learn new commands (because, honestly, nobody wants that anymore ).

Better test coverage (and now actually cross-platform)

Another big step forward is the improved test coverage, which now behaves consistently across systems:

Linux
macOS
Windows (yes, Windows got some love this time )

Error messages, symlink behavior, path formatting… all those cross-platform headaches?
FNPM now handles them.

This means FNPM isn’t just “usable” on Windows —
it’s reliable, predictable, and CI-friendly across all platforms.

️ Other cool improvements worth mentioning

New fnpm source command for shell integration
GitHub Workflows + issue templates for better contributing
Updated dependencies (thanks Dependabot )
Cleaner project structure with better dev tooling
A more complete test suite for future expansions

FNPM keeps growing with a focus on simplicity + power, not complexity.

A real example: turning `pnpm` into FNPM (without anyone noticing)

Here’s a real example of how easy this is.
I swear the first time you run it, you’ll feel that “oh wow” moment .

(base) ➜  awesome-project fnpm setup pnpm  
Selected package manager: pnpm  

 FNPM hooks created successfully!

Setup Instructions:  
Unix/Linux/macOS:  
  1. Source the setup script:  
     source .fnpm/setup.sh  
  2. Or add to your shell profile (~/.bashrc, ~/.zshrc):  
     echo 'eval "$(fnpm source)"' >> ~/.zshrc  

Usage:  
  • Now you can use pnpm directly:  
    pnpm add some-package  
    pnpm install  
    pnpm run my-script  
  • Commands will be automatically redirected to fnpm  

Note:  
  • Hooks only work in directories with .fnpm configuration  
  • Use full path to bypass: $(which pnpm) command

Reload your shell:

(base) ➜  awesome-project echo 'eval "$(fnpm source)"' >> ~/.zshrc

Now try any pnpm command:

(base) ➜  awesome-project pnpm --help

You’ll see something like:

 This pnpm command is intercepted by FNPM  
Available commands:  
  install, add, remove, run, list, update, cache, clean  

Use 'fnpm --help' for more information

Boom.
From that moment on, you keep using pnpm like always…
but FNPM is the one doing the heavy lifting behind the curtain.

No workflow changes.
No broken scripts.
No new habits.
Just smooth developer life.

✨ In short: FNPM is no longer “used”… it’s felt

With this transparent alias system, FNPM stops being a command you remember to type, and becomes:

fast
consistent
cross-platform
and completely invisible when you want it to be

If it was useful before, now it feels… kinda magical, honestly.

PS: we used AI to help us write this article — because great tools deserve great storytelling.

Documentation here

FNPM: The Package Manager Drama Ends Here

Thu, 02 Jul 2026 17:18:53 +0000

FNPM: The Package Manager Drama Ends Here

Hey devs! Tired of the endless debates over package managers? Ever wished for a solution that brings peace to the package manager wars? Meet FNPM – because life's too short for package manager drama!

I work at Konstruct.io we have free Fridays, and this idea was stuck in my mind for a while. I finally took advantage of AI to bring it to life! So please give us ⭐️ on konstructio/kubefirst, a great and amazing way to setup your kubernetes infrastructure following gitOps Philosophy.

What is FNPM?

FNPM stands for Fuck NPM. It's a tool designed to end the eternal conflicts between npm, yarn, pnpm, and others by supporting them all seamlessly. Think of it as the peace treaty in the package manager soap opera. ️

Why Should You Care?

Universal Support – FNPM supports multiple package managers, including npm, yarn, pnpm, bun, and deno. Use your favorite; FNPM has your back!
One Lock File to Rule Them All – No more lock file conflicts! FNPM ensures consistent dependencies across your team, regardless of individual preferences.
Happy CI/CD – Standardized workflows and consistent builds mean no more "works on my machine" excuses.
Team Harmony – Let developers be developers. Stop the package manager wars and focus on building awesome stuff!

How to Get Started

Getting FNPM up and running is super simple:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/ideascoldigital/fnpm/refs/heads/main/install.sh)"

Then, just use it like you would with your preferred package manager:

fnpm setup

And boom! Your dependencies are managed without the drama.

Basic Commands

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

Final Thoughts

FNPM is here to bring harmony to your development workflow. It's easy to install, easy to use, and might just save you from the package manager drama. ️

Check out the official docs here FNPM Documentation

Have you tried FNPM? Let me know what you think! ✨

Coder Legion - Recent posts tagged pnpm

FNPM Just Became Invisible (In the Good Way): Transparent Alias, Better Tests & a Smoother Experience

Before: npm, pnpm, yarn… drama.

Now: use whatever you want. FNPM does the hard work.

How does this alias magic works?

Better test coverage (and now actually cross-platform)

️ Other cool improvements worth mentioning

A real example: turning pnpm into FNPM (without anyone noticing)

✨ In short: FNPM is no longer “used”… it’s felt

PS: we used AI to help us write this article — because great tools deserve great storytelling.

FNPM: The Package Manager Drama Ends Here

FNPM: The Package Manager Drama Ends Here

What is FNPM?

Why Should You Care?

How to Get Started

Basic Commands

Final Thoughts

A real example: turning `pnpm` into FNPM (without anyone noticing)