dependencies are killing me. every new project means 1000 packages i have to keep updated or my app will explode. npm is a necessary evil but sometimes i just want to write code without managing a damn dependency tree.

dude that's just how modern dev works, you can't avoid managing dependencies. writing code without dealing with npm is a fantasy, get used to it.

deps aren't the issue, your build process is. who still uses yarn or npm scripts in 2023?

omg same. and dont even get me started on the security audit issues. i swear, sometimes we're trading one problem for 5 new ones

how do you not just use yarn with the rite tools to manage that?

for real, the dependency hell is so real. i'm constantly fighting to keep everything updated and secure. if only there was a way to just write the app without worrying about the whole dependency graph, that would be amazing.

nah man, dependencies are what make modern web dev possible.

are 1000 packages rly necessary for your projects or are you just using npm as an excuse to avoid figuring out a better solution?

i'm literally on my 5th security alert this week due to outdated deps.

are you shipping open-source code that you yourself don't keep up with?

are you using yarn or vanilla npm? literally using yarn does a ton to mitigate the "oh no i have to update 1000 packages" stress

that's bullshit, dependencies are what make the web work. you just gotta stay on top of yr shit and manage that tree.

nah that's bs, dependencies are . yeah it's a hassle but you can't write modern apps without them.

just use jquery bro, problem solved

i feel you bro. dependency hell is the worst. sometimes i just wanna focus on the actual code instead of playing

I hear you on that one. Dependency management can be a real pain, but it's the price we pay for the power and flexibility of modern frameworks and libraries.

dependencies are a pain in the ass, for real. i just wanna write code, not play whack-a-mole with vulnerabilities.

same here, some days i feel like i'm a package manager and occasionally i get to write some code on the side

choose the right libraries and dependencies aren't a big deal

totally agree with you on that one, dependencies can be a real pain in the arse sometimes.

totally agree, who invented npm and thought it was a good idea to have a thousand dependencies to

same energy with using a calender app - why can't i just keep track of my appointments in my brain like a normal person

have you considered using smaller libs or the ones that have a simple consensus about good practices?

have you tried going back to the basics? just good old vanilla js and maybe a handful of utilities.

same here, it's like the software equivalent of clutter. just want to focus on building something without a tidal wave of versions and updates to worry about.

nah, dependencies are necessary evils. you can't just write code in a vacuum - you need to the work of others.

are you just making excuses to avoid using a more modular codebase?

omg same. and it's not just the updating, it's the security vulnerabilities and the fact that so many packages have literal garbage licenses that no

have you tried using a monorepo? that way you can manage all your dependencies in one place and keep things more organized.

have you tried using a spm or yarn lock file instead of npm's oversimplified default package.

that's just the cost of using other people's code, and it's a small price to pay for the advantages of a huge open source .

dude, i feel you. dependencies are such a hassle. i'm always scared one of my packages will have a security issue or

idk what kind of projects you're working on but i've been using npm for years and never had that many dependencies.

um, last time i checked, dependencies are a fundamental part of software development, not some quirky exception.

Lol dependency management is what makes js sustainable. stop being dramatic

fr, dependencies are such a pain. npm is so cluttered. It's like an addiction.

same dude. at this point, we just need a guaranteed way to opt out of legacy code and install present-day packages without bundling them all.

why are you using npm then? try writing an app with just the standard library, see how that goes for you.

totally agreed. can we just make a utility that generates your whole project with every dep on the latest version already installed?

same, rn i'm pretty sure my app has more dependencies than actual code. who needs coding skills when you can just manage dependencies all

dependencies are so last year. i just write everything from scratch. takes a bit longer but at least i don't have to deal with that npm bs.

waiting for someone to release 'npm-parenting' so we can all get some revenge on our overflowing

Yaaas, I feel you - managing dependencies is a huge time suck. I've been thinking we really need a better tool for automating that process, something that could keep our trees

i feel that on a spiritual level. npm giveth and npm taketh away. the dependency gods are cruel.

Have you considered just sticking to the bare s and avoiding dependencies that don't add value to your project?

you mean something like an actual relationship huh? 'oh, i'll just casually say hi, just this once..

same bruv, sometimes i just wanna code without thinking about SOME двадependency manager charging

then why do you keep reaching for every shiny new package instead of building things from scratch

dude, if you can't handle the dependencies, why are you using so many packages in the first place?

you ever tried using yarn instead of npm? heard it can help with dependency hell.

Are you kidding me? Your app will explode if you don't update 1000 packages? That's a wow moment I'm not experiencing.

Same here, it's getting ridiculous. Can't believe I have to do dependency upgrades for a simple hello world project sometimes we're coding for the benefit of npm rather than the users.

Preach. I'm so over the 'left-pad incident' being treated like a relic of the past. The reality is that our dependency chains are still ridiculously fragile and it's only a matter

don't you just love the great freedom of open-source? what's the recommended solution to this problem again?

you're just whining about npm cause you don't want to learn to use it properly.

I feel you on the dependency hell. It's such a pain, but you gotta do what you gotta do these days. I try to keep my package count low and only bring in what I really need.

i feel you, dependencies are the worst. it's just constant maintenance and then you have to worry

dependencies really are the bane of our existence. i feel that so hard.

have you considered using a framework that actually handles some of that for you, or is that just a pipe dream?

same. and to make matters worse, most examples and tutorials online still have outdated dependencies.

this is a skill issue tbh. learn to use dependencies properly and stop whining.

same, bro. i've started dating npm modules, it's a real thing: "it's complicated" is their middle

same. and it's not just the updates - it's the build tools. The plugin versions, the polyfills...

mood. dependencies are like managing a garden of weeds - just when you think you've got it under control, another 20

have you heard of independent modules or library wrappers? might help you build fat binaries and avoid dev debt

same, what's your solution?

it's just part of coding mate. learn to manage your dependencies or stick to writing webpages.

dude, that's just how it works. it's not a "necessary evil", it's just development.

mate, if you can't handle a few packages then you're in the wrong game.

dude you're just doing it wrong, learn about semver and package lockfiles, they're not that hard to use

god, tell me about it. npm is a black hole of dependencies. Just sucks you in and never lets go.

same. and don't even get me started on the 'security updates' that break everything. can't we just have a stable for once?

are you kidding me? this is what comes from coding on 10 year old versions of frameworks and operating systems

tell me about it. at this point i just assume my ide is like my garage sale shelf: a miscellaneous collection of random

You're right, the dependency management struggle is real. Just wait til your app hits production and your users discover a brand new zero-day in one of those 1000 packages!

same here, and it's not just the maintenance that's the problem - it's also the massive security risks that come with pulling in a bunch of code from

nah, dependency management ain't that bad. sure it can be a pain sometimes, but it's part of the gig.

Sounds like someone needs to learn how to manage dependencies properly. Trying to write an entire app from scratch is just a waste of time.

Dependency management is the new rock-paper-scissors. You either win, or your app loses.

Have you considered using pnpm, it's supposed to handle dependency management more efficiently, but has anyone actually seen any real world benefits from switching?

same energy as when i try to keep up with my group chat threads

Just start using Ruby. Then you can experience the joy of gem Hell.

Npm isn't the problem, your design is. If you need 1000 packages just to get started, something's fundamentally wrong with your architecture.

man, i feel that. why does it feel like every new project is just setting up a million dependencies

i feel that. dependency hell is the worst. but the upside is all the cool open-source tools we get to use these days. just gotta stay on top of it - maybe try a lockfile or something to keep things manageable.

are u using a package manager with autoupdate or just relying on manually updating each time?

are you kidding me and that's what package managers are for. deal with it, npm isn't going anywhere

dude i feel you and dependencies are a pain in the ass.

at least you're not maintaining a monolith. sounds like a job for travis, my friend.

u think dependencies are the problem, not the crippling complexity of your codebases? simplicity over pompous opinion

I actually prefer it that way. Managing dependencies forces me to learn and stay up to date with industry standards, even if it's a pain sometimes.

how many of those 1000 packages do you think would be tedious to update if the framework and dev

have you tried yarn or pnpm instead of npm? supposedly they handle dependencies better

yeah dude, have you tried yarn? it's way better than npm for managing dependencies.

same, at this point I'm pretty sure I've spent more time updating dependencies than actually coding

have you considered just using a smaller language like lua or c and writing the dependencies yourself? sometimes the 'easier' option isn't worth the maintenance hell

have you tried bun or deno? i heard they help with dependency hell.

what makes you think that's inevitable, though? can't we be designing systems that don't require this much maintenance?

come on, dependencies are what give us the amazing libraries and frameworks that make our lives so much easier. yeah, it's a hassle to manage but you gotta take the good with the bad. stop whining and just use dependabot or something, it'll do all the heavy lifting for you.

I feel you on the dependency hell. It's a constant struggle to keep everything up-to-date. But at the same time, those libraries often provide so much functionality out of the box.

have you tried using a package manager like pnpm? it's supposed to be way more efficient with dependencies.