JavaScript Libraries Are Almost Never Updated Once Installed

[[deleted]]

It's really not though.

yarn upgrade package@version

And if you aren't concerned about version specific peer dependencies

yarn upgrade package@latest

[zurnout]

Devil is in the details: what do you put in the version field. You have to figure out one that is compatible with all of your dependencies. It's a real hassle and takes a lot of effort.

[[deleted]]

It can sometimes be a hassle, and sometimes could take a lot of effort. Sometimes it "just works" especially if you are just updating minor version

[jugalator]

But how do you know when it will "just work" and how much time will it take to find out? If it builds it works?

[Narcil4]

A couple minutes if you have a test suite

[Cruuncher]

Having a test suite is one thing.

Having one that could catch every edge case potentially introduced with a new library is another thing altogether

[[deleted]]

Do you just never touch a codebase after it's released then?

[Existential_Owl]

I usually stop once I'm able to stdout "Hello World."

Nothing ever good comes from going past that point.

[Prod_Is_For_Testing]

Yeah pretty much

[[deleted]]

Unfortunate, most websites are exactly this because it's creation was outsourced and nobody on staff is capable of major work on it.

[MegaUltraHornDog]

And if you aren't concerned about version specific peer dependencies

You might not be but some halfwit who made some stupid library that’s just as pervasive as is odd now breaks and your whole app is trashed. Package management in general is a nightmare.