JavaScript Ecosystem Trade-Off: Code Size vs Dependencies

𝗧𝗵𝗲 𝗥𝗲𝗮𝗹𝗶𝘁𝘆 𝗼𝗳 𝗠𝗼𝗱𝗲𝗿𝗻 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 Your actual application code might be just a few hundred KB… but the dependencies behind it can easily reach several GB. That’s the power and trade-off of the JavaScript ecosystem — faster development, reusable packages, and a massive open-source community. Sometimes the real weight isn’t the code we write… it’s the packages we install. 😅 GeeksforGeeks w3schools.com #JavaScript #NodeJS #WebDevelopment #Programming #Developers #ReactJs #MERN #ExpressJs #AngularJs

  • No alternative text description for this image

This is not only for Node.js builds, even Cargo builds are just way too huge.... the build installer from Dioxus or server build will be maybe of approx. 50 mb size.... whereas the build dependencies stored for compiling take 20-30 GB in total for a whole full stack.

Which is why I’ve always gone against the grain and refused to use ANY 3rd party libraries. I can’t stand a project that carries enormous amounts of (never-utilized) baggage to incorporate maybe one useable thing that no one felt like building on their own.

installing them at times takes like 50 mins in some cases, talk about npm i everything lol

So true. The node_modules folder is often bigger than the entire project. It’s a good reminder to be mindful about adding dependencies.

Especially those UI libraries. In my initial days of using react, I will install about 4 ui component libraries, stack Providers on top of providers like am building a pyramid lolz 😆

Say what you want to say about JavaScript! I love it!

See more comments

To view or add a comment, sign in

Explore content categories