DEV Community: Jairo Fernández

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

Jairo Fernández — Fri, 14 Nov 2025 07:47:36 +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 🚀

Jairo Fernández — Thu, 13 Feb 2025 07:16:26 +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! 🚀✨

The sad story of node update!

Jairo Fernández — Wed, 14 Aug 2024 00:37:19 +0000

Yesterday, I was happily finishing an upgrade at work, and everything seemed perfect 😄. All the dependencies migrated smoothly, and my npm audit looked great 🚀. But then…

Server-Side Request Forgery in axios ⚠️
https://github.com/advisories/GHSA-8hc4-vh64-cxmj

I spent a lot of time fixing things, only to see that stupid message 😡. My OCD was driving me crazy 🤯.

And, I said, hmmm how exactly this error works? what the hell is SSRF? I'll try to explain fast the concept and share with you the discovery :D

SSRF, or Server-Side Request Forgery, is like tricking your server into being an unintentional errand boy 🕵️‍♂️. It’s when a hacker gets your server to make requests to places it shouldn’t, kind of like sending your dog to fetch a stick but it comes back with a bomb instead 💣. (from ChatGPT 😍)

In code please!

Normally, axios works, in your server when you need to do some external request to https://some-domain.com/api/, you can do something like this:

const instance = axios.create({
  baseURL: 'https://jsonplaceholder.typicode.com/',
  timeout: 1000,
  headers: { accept: 'application/json' }
});

In theory, this is our innocent and pure server meant to fetch resources from jsonplaceholder:

const axios = require('axios');
const express = require('express');

const instance = axios.create({
  baseURL: 'https://jsonplaceholder.typicode.com/',
  timeout: 1000,
  headers: { accept: 'application/json' },
});

const app = express();
const port = 3000;

app.use(express.json());

app.post('/fetch-data', async (req, res) => {
  const url = req.body.url;
  try {
    const response = await instance.get(url);
    console.log(response.data);
    res.json(response.data);
  } catch (error) {
    console.error(error);
    console.log('URL:', url);
    res
      .status(500)
      .json({ message: 'Error fetching data', error: error.message });
  }
});

app.listen(port, () => {
  console.log(`Server running on http://localhost:${port}`);
});

You can try this one on terminal:

curl -X POST http://localhost:3000/fetch-data \
 -H "Content-Type: application/json" \
 -d '{"url": "/todos/1"}'

The response is like this:

{"userId":1,"id":1,"title":"delectus aut autem","completed":false}

everything is beautiful, but...

Now, if you have another server (acting as a malicious server) on http://localhost:4000, what happens when the user tests it:

const axios = require('axios');
const express = require('express');

const app = express();
const port = 4000;

app.use(express.json());

app.get('/private-data', async (req, res) => {
  const url = req.body.url;
  try {
    console.log('Private URL:', url);
    console.log('WTF??????');
    res.send({ message: 'Data fetched' });
  } catch (error) {
    console.error(error);
    console.log('URL:', url);
    res.status(500).send('Error fetching data');
  }
});

app.listen(port, () => {
  console.log(`Server running on http://localhost:${port}`);
});

Try again

curl -X POST http://localhost:3000/fetch-data \
 -H "Content-Type: application/json" \
 -d '{"url": "//localhost:4000/private-data"}'

you will get this response:

{"message":"Data fetched"} # data from other server!

“So, this is really bad 😱 because you’re trusting the axios instance. The good news is that within a day, the issue in axios was successfully fixed in version 1.7.4 🎉.”

If you want to play with this, please check the experiment here 👇

Docker is destroying my machine! 💥

Jairo Fernández — Fri, 26 Jul 2024 01:52:20 +0000

CLI Maker: More Than We See

Jairo Fernández — Wed, 24 Jul 2024 02:25:15 +0000

Build your ideas so fast!

https://www.npmjs.com/package/@ideascol/cli-maker

npx @ideascol/cli-maker

We are creating and improving cli-maker, and when I showed my partner the latest version, he said to me, “Hey man, you can’t see this advantage directly by looking at the create command or checking the readme.” So, I decided to write this simple and short (I hope) article. ✍️📄

Complete and simple CI configured 🚀

You just need to add a secret NPM_TOKEN to your repository. Now, when you create a PR on Github, you’ll see the testing job running on the actions tab. When you merge or push code to the main branch, you will see 2 jobs: testing and publish job (for publishing, you need to change your package.json version manually).
I think it’s great to see that configuration without any effort. 👍✨

Automatic Library exportable to npm 📦

Your library is usable (folder src/lib) using an import like this: import { AwesomeThing } from '@company/your-library' 📚

Automatic binary CLI 🛠️

Your library, of course, is usable using npx @company/your-library. Your users will have access to your functionalities so fast! ⚡

Setup unit testing without any extra dependencies 🧪

Testing in Node.js, or in general JavaScript, is totally broken for me. Jest, Mocha, any new flavors, it’s a terrible thing (yes Jest, forgive me, you know how I love you). In Node.js 20, we finally have native testing (test runner Node.js 20 LTS). 🥳🎉

So, that’s it! I hope you enjoy and check it out for yourself. 🙌😊

Create a simple CLI, a mess

Jairo Fernández — Sat, 20 Jul 2024 20:44:11 +0000

In all my different jobs and personal projects, whenever I needed to create some kind of console application for any purpose, I always started from scratch. I used bash scripting, Cobra (Golang), Commander.js (Node.js), and even Dart and PHP. However, I always ended up with a bad taste in my mouth. Why? Starting the process is terrible 😩 (I guess the best starting point is with Cobra 😅). Checking the structure, discussing the correct place for the code, or simply putting all the code into a copy-paste example with 1000 options turns this simple task into a mess… 🤯

Aha, I decided to contribute to the chaos by creating my own library in Node.js. However, I have a strong stance about node_modules, I haven’t felt good about the huge size for simple things: too many testing frameworks, compilers, etc. I recently heard about Node.js LTS (20), which allows you to use the native testing library. I thought, I can support typeScript and @types/node as dev dependencies. It’s not perfect, but it’s just two dependencies.

The next challenge for me was configuring the CI, unit testing, and dealing with the garbage produced by GPT-4 trying to help me create this as an experiment, which ended really well 😅. (Don’t kill me in the future, AI, I am faithful to the machine cause 🤖.) But I need to recognize that this work would have been impossible to do without using GPT-4o in just one week! After my normal job, with a lot of coffee ☕, so thanks, GPT-4o! 😄

Which characteristics do I need from a CLI maker, that is the name of the library

I need to start from zero with just one command; I hate to copy, paste, and rethink the same stupid things 🤦‍♂️
I need a simple structure supporting TypeScript.
I need a simple CI with GitHub Actions automatically set up.
I need the CLI exportable automatically.
I need to use my library like a simple package with and npm install and import in other parts.
I need support for an interactive CLI. I love the Symfony terminal—interactive, fast, great UX or something similar to Gum
I need to use the CLI in a direct mode passing the parameters.
I need simple types, I want to add emails, url, list and use them easily
I don’t want to configure 1 million dev dependencies
I want to see my commands and not want to vomit because of the mess 🤢

Yeah, I'm not picky, but I wanted something like this for myself 😅.

So, hands of work, I would like to present you cli-maker my own version of the hell, just execute this command and check the magic,

Go to an empty directory and use Node 20 (I’ll add this validation, I promise you 😉)

Go to library if you want to skip this lecture npm @ideascol/cli-maker

npx @ideascol/cli-maker

And that’s it, you will see the usual installation process. Please be patient 😊.

Trust me, proceed… 😉

For now, I just have one command—the only one needed for now. Please proceed in an empty folder and fill in the data 😊.

Right! Now, create your own CLI 🚀.

npx @ideascol/cli-maker create

Fill data

If all was good, you’ll see this:

Let me explain to you in the next article how we can extract the best from this simple library… 📚✨

See you! 👋

Check the next cli-maker-more-than-we-see

Has tu README realmente útil

Jairo Fernández — Thu, 30 May 2024 02:13:42 +0000

Has tu README realmente útil

Muchas veces, el readme se vuelve un poco tedioso, y en ocasiones he preferido usar y abusar de scripts bash, para automatizar procesos, sin embargo, a veces puede resultar un poco difícil mantener ambas cosas, sobre todo en proyectos donde el cambio está a la orden del día, entonces, me encontré con una herramienta que ayuda a convertir los files markdown en obras maestras, muy similar a como usaríamos un Jupyter notebook!

manos a la obra,

La herramienta se llama runme, y básicamente tiene 4 modos de uso:

Con tu editor, por ahora solo con Vscode.
Vía terminal, donde puedes directamente ejecutar un comando de tu README (ya lo veremos!)
Vía terminal pero abriendo un servidor web, que “oh sorpresa”, es un Vscode corriendo en tu navegador.
Vía extensión web.

Veamos un ejemplo

Usando la extensión de Vscode: Runme DevOps Notebooks

Al presionar allí empezarás a ver la magia

Notarás que al acercar el mouse a una celda (sí, cada sección se llama celda como en los Jupyter notebooks)

En nuestro caso, vamos a empezar con algo sencillo, escribiremos el comando

uname -a

Y al ejecutar veremos como la salida de la terminal queda directamente en nuestro README

Veamos todo junto con un ejemplo más grande como se ejecuta

Usando su extensión

Sigue las instrucciones para instalarla [aquí], y si vas al repositorio donde tengo el código del ejemplo anterior,

https://github.com/jairoFernandez/articles/tree/main/readme-powers

Verás un botón que te dará un link de esta forma:

https://runme.dev/api/runme?repository=https%3A%2F%2Fgithub.com%2FjairoFernandez%2Farticles.git&fileToOpen=readme-powers%2FREADME.md

Esto abrirá tu vscode y te permitirá ejecutar el Readme.

DEV Community: Jairo Fernández

🚀 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 💡

The sad story of node update!

Docker is destroying my machine! 💥

CLI Maker: More Than We See

Complete and simple CI configured 🚀

Automatic Library exportable to npm 📦

Automatic binary CLI 🛠️

Setup unit testing without any extra dependencies 🧪

Create a simple CLI, a mess

Right! Now, create your own CLI 🚀.

Has tu README realmente útil

Has tu README realmente útil

manos a la obra,

Veamos un ejemplo

Usando su extensión

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