This really reminds me of most my interactions with the JS community. I'm sure not everyone is that way. Whenever my projects use FOSS I always remind them exa

This really reminds me of most my interactions with the JS community. I'm sure not everyone is that way. Whenever my projects use FOSS I always remind them exactly what a 'dependency' is. You should know and understand your dependencies and risks associated with relying on them. You need to be willing to lock-in to a version if need be or replace it entirely. Some developers I work with that throw together one-off web applications tend to inject dozens (sometimes hundreds) of dependencies (which they like to dynamically pull from latest builds) into their projects, enough to make me dizzy looking through the list. Typically development starts, they meet some initial goal and keep gluing more and more packages together to meet some goal/desired functionality. Then something breaks and they conveniently have other internal work that has to take priority, leaving a broken application they don't want to deal with for someone else to fix because they know it's an absolute mess they created. Rinse repeat. Now you've established an expectation of functionality you have no clue how to maintain and did not clearly explain that to your client when you took shortcuts to glue everything together.