web-dev-hub

A little background Before we begin, I would like to share with you with my personal opinion about the topic. Feel free to discuss this in the comments below. So, of course, 1M packages is a great success, or is it? If you're someone who has been into the JS ecosystem for quite a while now, you know how the situation really looks like. And, while 1M is indeed an impressive number, I think we all agree that only a small fraction of these packages are actually  useful . A great chunk of them is just a big mess - a  graveyard of code  that many of us (JS developers) contributed to. That's where these numbers come from. But why? Well, maybe it's because of NPM's  simplicity ? JavaScript's popularity has grown exponentially in recent times, and with that - NPM registry. The JS code that NPM houses is simple and portable - just like the registry itself. This brings the  "entry level"  pretty low, allowing beginners and starters to use it just like that. Naturall...

Every JavaScript project starts ambitiously, trying not to use too many NPM packages along the way. Even with a lot of effort on our side, packages eventually start piling up.  package.json  gets more lines over time, and  package-lock.json  makes pull requests look scary with the number of additions or deletions when dependencies are added. “This is fine” — the team lead says, as other team members nod in agreement. What else are you supposed to do? We are lucky that the JavaScript ecosystem is alive and thriving! We should not be reinventing the wheel every time and trying to solve something that the open-source community has already solved. 👋 As you’re diving into JavaScript dependencies, you might want to dive into AppSignal  APM for Node.js  as well.  We provide you with out-of-the-box support for Node.js Core, Express, Next.js, Apollo Server, node-postgres and node-redis . Let’s say you want to build a blog and you would like to use Gatsby.js. T...