Jopi.js : I'm the new community manager!

Clara TC — Tue, 09 Dec 2025 10:18:01 +0000

For me, IT is a recent career change

I started working with computers four years ago. It's a complete career change for me; before that, I was a lab technician, taking samples to detect various substances.

Learning the basics of IT was a real challenge. But little by little, everything became clearer.

And now, four years later, I'm proud to announce that I'm the Community Manager for the Jopi.js project! This means writing articles, making videos, and also answering your questions. All on a volunteer basis, because behind the Jopi.js project, there's not a company but a passionate individual... and now two passionate individuals :-)

For me, it's a great source of pride, because this role is a recognition of my skills. While I'm certainly nowhere near the level of Johan, the creator of this project, I'm still very proud!

As for his background, he's a technical guy. He talks about code, he thinks about code, and I even think he dreams about code at night! The problem with him is that everything seems simple to him. Obviously. Easy! ... and that's the issue, because he doesn't know how to adapt to beginners who don't have 30 years of experience.

My empathy is my strength

The reason they asked me to take on the role of community manager is precisely this: I don't have a high level of expertise, which is actually an advantage here. It allows me to better understand what needs to be said and how to say it.

I'm also an empathetic person, which helps a lot. It motivates me to do my best to explain things clearly.

I hope to do a good job and receive positive feedback. I'm not being paid for this, so for me, it's a bonus. It will also enhance my resume, which is currently a bit sparse. And one thing is certain: it will help me grow professionally.

I created the Jopi.js project website

I'm the one who created the project website (https://jopijs.com). Okay, you can easily guess my personality from it :-) ... also, the little character you see in the infographics represents me (I had a lot of fun).

The site breaks away from the serious websites you usually find in the tech world. There are two reasons for this. The first reason is that this site reflects my personality. The second reason is that Johan (the mastermind behind the project) wanted to create a technology that simplifies computing, not the other way around. And so, I thought it was good to make a "friendly" site that also exudes this feeling of breaking away.

So, there you have it, I wanted to write a short article to introduce myself a little. To explain who I am and why I'm here.

About Jopi.js

Okay, I still need to tell you a little about JopiJS and what it is. I'll simplify things by saying that Jopi.js is a clone of NextJS: a server-side technology based on NodeJS, used to build websites.

The goal of JopiJS wasn't to create a clone of NextJS; in fact, there are significant differences. Its aim, however, was to draw inspiration from the simplicity and speed that NextJS offers.

This desire for simplicity is JopiJS's strength, and what Johan is trying to enhance.

Personally, I was already familiar with NextJS, and I found it both simple and complex. Over the years, they've added interesting but complex features. Far too complex for me, as I just want to create a simple website without needing high performance or lightning-fast responsiveness.

JopiJS removes this complexity, making it much simpler. Ironically, benchmarks show it's 7.5x faster than NextJS!!! (proof in video here).

This extreme speed of JopiJS means there's no need to compensate with tricks that make things much more technically complex (that's how I see NextJS in its latest versions). So I have something simple, and at the same time, really nice performance! ... although in reality, for me, there's not a huge difference between displaying 11,000 pages/sec and 80,000 pages/sec. I usually create small websites to promote vacation rentals.

NodeJS - npx, super handy for running patches!

Clara TC — Mon, 08 Dec 2025 18:15:29 +0000

I'm going to talk to you about the npx tool, which is a standard NodeJS tool. I didn't really know this tool before, but now I love it; it saves me a lot of time!

I use it to easily deploy my NodeJS scripts to my servers and run them to patch data. Maybe you're familiar with this: you make a mistake, then you run a patch to try and fix it... okay, it happens to me too... sometimes :-)

What is npx?

npx is a tool that allows you to download and run a NodeJS package. If I use npx myPackageName, it will automatically download and run the NodeJS package myPackageName.

Run a NodeJS package?

In package.json there is an entry named bin which allows you to specify the name of a script that will be executed by npx.

{
    "name': "myPackageName",
    "version": "1.0.1",
    "bin": "./myScript.js"
}

When I do npx myPackageName arg1 arg2, it downloads the latest version of the package myPackageName and then executes the script ./myScript.js with the arguments arg1 and arg2. It's the same as if I were doing node ./myScript.js -- arg1 arg2.

So it's very practical!

The only small thing is that you need to add this line at the beginning of the script (a shebang): #!/usr/bin/env node. So at the beginning of my myScript.js file, I need to add this line. That's all!

What I used to do for my patches

Before discovering npx, I had scripts that I uploaded to my servers (zip, upload, unzip) and then ran manually. Then, when I updated these scripts, I had to upload them again to all my servers before running them.

With npx, there's no need to do that anymore! Because it automatically downloads the latest version of my package!

Creating a private repository is super easy!

I use the Verdaccio tool, which allows me to have private NodeJS packages.

This lets me create private packages that I can deploy very quickly on my servers, without errors, while also having a history of my previous versions.

When you publish a package, it's visible to everyone. But with a tool like Verdaccio, you can easily have a private repository.

Okay, I'm going to make you smile... npx verdaccio... there you go, it's installed on your computer! All you have to do is open the URL http://myPrivateNpmServer:4873/ in your browser to see for yourself!

The Verdaccio welcome screen will tell you what to do to create a login/password. It's very simple!

Once that's done, you just need to do this on your servers so they use Verdaccio: npm set registry http://myPrivateNpmServer:4873/.

That's it! You now have your own private repository!

Complete Example

Here I'm going to show you a complete project that you can copy and paste.

package.json

{
  "name": "myPatchName",
  "version": "1.0.0,
  "scripts: {
    "publish": "npm publish --registry http://myPrivateNpmServer:4873/"
  },

  "bin": "./myScript.js"
}

myScript.js

#!/usr/bin/env node
console.log("Executing my patch!");

And that's it!

To debug the script, simply run npx myPatchName in the local folder. It will automatically use your development version.
To publish the script, simply run npm run publish in the local folder.

Forem: Clara TC