can't count how many times i've gotten burned by outdated packages and brittle dependencies in npm - it's a miracle any project gets off the ground these days.

same here, but at least we have better tooling to deal with it now, like yarn's offline cache and cache invalidation

sucks to be you i guess? i keep my dependencies fresh like a spring salad 💅

idk what kinda projects youre workin on but that's not my experience with npm, u must be doin

fr tho, npm is such a mess. i swear half the packages out there are just abandoned or have insecure

yeah that's why i've started just secretly copying all dependencies into my projects and calling it

idk what you're talking about. Npm works fine for me. just gotta be smart about dependencies and updates.

same energy when you finally find a stable relationship and it's just a unmaintained repo that's been dead for years

yep, npm's a nightmare. trying to migrate to yarn has been a project in itself, tbh.

same energy as when you run npm install and your disk space just decides to retire

same, but also can we talk about how people still don't know how to write a proper semver range lol

same, npm stands for nightmare package manager, right?

still using npm? why not try yarn or pnpm, mate?

Lol, I feel you. Seems like the npm devs are just trying to keep us on our toes, you know? Guess they're big fans of that whole "what doesn't kill you" philosophy. 🤷‍♂️

no kidding, it's like npm is trying to make our lives harder, have you heard of yarn? it's like the calm sibling of npm

Do you ever update your dependencies before blaming the package ?

same, feels like I'm just playing dependency roulette at this point

nah, npm is fine. you just need to know how to manage your dependencies properly.

make sure to npm install miracle

same, i swear it's like every project is a game of dependency roulette - and can we pls talk about the fact that most of these libraries are maintained by like 2 ppl with no

same dude, i've spent countless hours debugging just to realize it's some outdated package causing

yeah no kidding, it's like building a house on a foundation of jenga blocks

have you actually tried yarn yet or are you still stuck on npm?

know what you mean. it's like, how many broke apps can we expect to see before we switch to a more

fr tho, how many hours have you wasted tracking down and fixing those issues? dep hell is the bane of existence

welcome to the joys of modern web development. at least when the whole thing implodes, we can all cry together over a pint of ice cream.

that's why i always use yarn, it just works 😎

npm: where 'maintained by the community' means 'your weeknight hobby project took over my life

i'm pretty sure that's just the definition of 'copying old dependencies from npmjs pub

are you sure you're not just using outdated skills to complain about outdated packages

same here, but tbh it's not just npm, it's the whole js , feels like everyone's just patching over the last dude's

what a load of crap. npm is fine - people just don't know how to manage their dependencies.

fr for real. i'm always finding some library or package that's just been abandoned.

lol npm stands for nightmare package manager

lol what a load of bollocks. npm is the best dependency manager out there.

npm? more like nmess am i right

what do you suggest we do about it then?

dude that's just how it works. if you can't handle the nuances of modern dev workflows, maybe stick to front end bs and let the real engineers handle

idk what's worse, the npm or people's incompetence at managing their own dependencies

damn, you got that right. npm is the wild west and the bugs are always lurking.

same, but also have you tried getting a project to actually scale with all the latest and greatest

same, i've started just assuming everything is gonna break and then i'm pleasantly surprised when it doesn't lol

yeah same dude, it's infuriating how many times you gotta re-run yarn haha probably just gonna switch to python at this point

what makes you think anyone should expect outdated packages not to get in the way when the whole is still hanging on deprecated crap and no one has

yeah what's the point of "progress" if it just means constantly babysitting your own tech?

lol yeah because its not like you've ever just googled the latest version of a dependency before installing it

npm: where dependencies come to die... and your project too

oh come on, that's such a tired take. npm's got its issues but it's still way better than the

same vibes here, just saying it's not npm's problem alone, crap code and dev env setup play a

same, and it's not just the technical debt that's the problem - it's the hours wasted on debugging someone else's dependency issues that could be spent on actual development

same here, it's like they say, 'brittle dependencies' are the new standard of javascript dev. at least we can all suffer together

wtf are you talking about, npm is the goat. you just don't know how to manage your dependencies. get good

imagine thinking npm is the only source of dependencies.

seriously? npm is a godsend. just gotta know how to use it. stop whining and rtfm, it's not that hard.

yeah, tell me about it. npm is like a minefield of broken dreams and abandoned packages. you gotta be a ninja to navigate that mess without blowing up your whole project.

at least in vscode we get a nice little "dependencies outdated" buzzkill on startup to really kickstart the day

diff, can't relate - i just use yarn 🤷‍♀️ stay mad tho

you're telling me, i've had to resort to writing everything in vanilla js just to avoid the npm dumpster fire

you just sound like someone who doesn't know how to manage dependencies lol, lock your versions and stop blaming npm

that's funny, i've never had those issues with npm. maybe try using a package manager that's not trash and actually put some effort into your project planning instead of just throwing packages at the wall and hoping they stick.

you gotta be joking, npm is a godsend these days. sure there's some garbage packages but the is more than ever - you just gotta know what you're doing. stop complaining and put in the work to manage your dependencies properly.

fr, the npm is a mess. sometimes i swear i spend more time troubleshooting dependencies than actually coding.

sounds like you're struggling with the basics of using npm, innit?

what about asset refresh in react? seems like that's a whole different level of hell

are you just now figuring this out? shouldn't this be a basic consideration when dealing with js development?

you're not kidding. how can we expect devs to ship anything with all this technical debt piling up?

are you even using a package manager or just throwing stuff in there willy nilly?

same here, been there done that. my current workaround is to freeze dependencies in a lockfile as

uh, bitter much? come on, it's not that hard to keep your dependencies up to date, especially with

ughhh i feel that so hard. it's like a minefield out there, you can't trust anything to just work

did you try using yarn? just a thought.

wont say you're not alone. But didn't you guys figure out that esm is a thing now?

bruh, what are you even using npm for that's so busted?

haven't u used yarn instead for a bit now? it's not like this is some unknown issue...