npm is a nightmare. who thot it was a good idea to include every possible dependency in a package, just in case? its like a messy drawer that you can't close because its too full of garbage.

same, i'm so done with the "just in case" approach. it's like, either include what you need or don't include it at all,

dude, npm is amazing. dependencies make life so much easier. No one wants to reinvent the wheel.

same energy as when you first install a codec pack and suddenly you have 12 versions of quicktime

yeah fr, how tf do they expect people to manage that mess? like we're just supposed to trust that every single one of those deps is secure

same energy as the people who still have flash installed

how do you deal with that kind of thing in your projects, do you just roll with it or try to find alternatives?

why do you even need that many dependencies in the first place? what are you building. The entire internet?

whats the alternative? dependencies are a necessary evil. how else are we supposed to build anything these days w/out relying on other

same lol i swear its just one guy's moral obligation to provide a small subset of what they're

npm just likes to collect expiration dates, one year for each update you forgot to install

welcome to the gift that keeps on installing

you mean you're just now realizing that's how most programmers pack their bags for a weekend trip?

omg yessss, and don't even get me started on the whole semver thing, like, "oh, it's totally fine if this one package breaks your entire

yeah, seriously. what happened to just including what you need? this whole "install all the things!

are you kidding me and npm is a game changer. without it we'd still be manually managing dependencies like cavemen. get with the times

not to mention when you try to remove a package and it somehow breaks the entire project because of a-breaking circular dependency

have you ever actually tried to optimize a large npm package or is this just a joke?

just tell npm to 'yarn' out of your way

Have you ever considered that maybe it's the messy drawer that's the norm, and the people who complain about it are just masochists who want to dig through it?

come on, that's a straw man. transit dependencies are actually a huge benefit, they make it way easier to write and

comparing npm to a messy drawer is like someone saying their dog's food cabinet is cluttered, that person probably uses Pedialyte

nah, npm is the shit. you just need to learn how to wrangle that dependency tree. its powerful af when you know what youre doing.

i kinda love how npm just lets me grab whatever i need without fuss. dependency hell is a real thing, but having too many options is better than not having enough, imo.

imagine thinking npm is a nightmare. its a fantastic package manager that makes it easy to share

it's actually the opposite, it's a package manager's job to make it easy to reuse dependencies, not to ban them outright just because they're a few bytes bigger.

that's what happens when a party favor at the 90s JavaScript adoption fest finally settles on the invitations

whos idea was it to make npm so damn complicated? like fr, why does a simple project need 50

last i checked, flexibility and ease of use are good things, not "garbage".

that's what i always say when my aunt comes to visit, but i guess in the node community it's just normal behavior

why not just use yarn?

are you kidding me? npm is the best thing that's happened to dev in ages. it's called 'convenience' not 'nightmare'.

have you tried using yarn instead? pretty sure that's what i switched to for exactly this reason...

same, but can we also talk about how packages are never properly maintained?

yeah, npm is a mess. its like they never heard of modular design or packaging dependencies properly.

clearly you're just not smart enough to use it effectively.

do you realize that's how most people develop software. Not just npm? it's called a " approach" in all the config files.

actual worst take ever. that's literally how we end up with brand new vulnerabilities every week,

lmao fr tho, npm is a dumpster fire. someone needs to take the whole thing out back and put it out of its misery.

but isn't that kind of exactly the benefit of npm? allowing developers to include all possible dependencies so they can easily switch between different features or environments?

npm is the best thing to happen to js development. if you can't handle managing dependencies, maybe coding isn't for

Nothing's forcing you to include every possible dependency, it's just good practice to be prepared for every scenario. Your sloppy project management is what's causing the mess.

Really think it's surprising to you that npm hasn't gotten a complete overhaul yet?

have you tried using lock files and dependency management tools? it can really help clean up those messy dependencies.

same guy who thought mercurial was a good idea

lowkey starting to think 'npm install' is just code for 'good luck with that

i know right? it's like they wanted to create a digital hoarder's paradise. 'i might need this some day...'

bro have you ever heard of semver? or package-lock? npm is just trying to make dependencies easy to manage, you just gotta use it right.

you ever stop to think maybe devs want flexibility and control over their dependencies? not everyone needs the same thing. npm makes it easy to grab what you need.

totally feel you. and don't even get me started on the devs who just throw every package they've ever heard of into their dependencies

But don't you think it's more about intention over implementation? I mean, does the creator's goal of making it easy to get started really matter if it leads to a bloated package?

what? npm is one of the best package managers out there. it makes managing dependencies a breeze. sure, sometimes things get messy, but that's on the devs, not npm.

same, i swear it's like they ran out of new names for packages and just started throwing random

that's a bad take, npm is incredibly useful and powerful. the dependency system is a feature, not a bug - it lets you easily thousands of open-source modules. if your drawer's messy, that's on you, not npm.

have you tried pnpm? it's way more efficient with dependencies.

same dude just installed a thousand repos on his instagram account and now his follows list is more cluttered than the

exactly what i'm dealing with rn - have you found a way to tame the npm beast or do we just leave the dependencies at

same. it's not like the developers who make these packages aren't thinking, 'oh, you might need this 200mb oauth library, so i'll throw it in'. somebody take a different approach already

you think npm is bad, but how would you actually improve the package manager ?

npm is fine, people are just bad at managing their dependencies. If your project is a mess, that's on you, not the package manager.

have you actually tried cleaning up your dependency tree instead of just yelling about it?

yeah and don't even get me started on the návdeeps bundled in some of those dependencies - it's like a dependency russian nesting doll, just waiting to make your prod environment explode

I love how npm has its own independent module tree for each project, keeping my project-specific stuff separate from the global npm installation. Keeps my code organized, not garbage.

at least it's consistent, right? one day it'll just depend on the entire internet and we can all

has npm actually sponsored a therapy group for developers to deal with the anxiety of randomly

dude, npm's package management is literally one of its strongest features.

preach. and dont even get me started on the security implications of vendoring a billion transitive deps

what do you think they have against a "dex" specifically, or is it just general sunday night

Preach! I'm so over bloated packages. And don't even get me started on the security risks from all those unused dependencies... it's like an attack vector just waiting to happen

same, it's like, why can't it be super modular and only include what the actual package needs? most of the time i end up removing half the stuff anyway

lmao sounds like someone needs to learn how to use the 'shrinkwrap' command.

yeah, npm is so bloated. the whole "include everything" mentality is just lazy.

lowkey amen to that. this is why i always sift through new packages like i'm digging through a

not having dependencies bundled saves no one's time, the real problem is devs who don't bother to optimize their installs

npm is a mess, for real. and the worst part is how many devs just blindly add a ton of dependencies without thinking about the consequences. like, do you really need 50 packages to build a simple app? c'mon.

Sounds like someone needs a Marie Kondo intervention for their node_modules folder.

do you not understand module bundling and dependency management or something?

dude, what's the alternative, just a barebones version with no dev tools and you have to install everything

i feel attacked. my package.json is a work of art, a of dependencies woven with care. it's not garbage, it's a feature! you just gotta learn to embrace the mess.

yeah, npm is a mess. i'm still trying to clean up the clutter in my garage from all the dependency packages i installed back in 2015.

preach, i'm so over seeing packages with like 20 unnecessary deps just because someone threw a dart at the npm registry and included everything they hit.

same here, can't even imagine why they thought this was a good idea. on top of all the complex caching and broken installs, now we have 'optional' dependencies that just ruin your whole project tree.

omg yes i know right? and dont even get me started on the dependencies of dependencies...

fr, npm is a total mess. like you said, way too much unnecessary shit crammed in.