- Joined: Sep 5, 2012
- Last Login: Jan 11, 2022, 1:10pm EST
- Comments: 408
Share this profile
I hadn’t heard of colors.js and my first thought was it was a helper library that like, helped with CSS color palates or something in a way that would be difficult/impossible to do with just the math, etc. built in to CSS, but, no.
I guess the question is if the library (esp. the corrupted version) fails gracefully, giving the user monochromatic console output. If it DOESN’T, well, then you’re left with console output you can’t read, which…. obviously would make it hard to troubleshoot the problem?
Comment 1 reply
Why would that happen? The idea is you pin a a version of each of the packages that you know works together for say, version 1.0 of your project.
Then for version 1.1, you do the same. If you need to add a new package and that requires that one of your dependencies gets updated, well, you do that and ensure that it didn’t break anything else, and if it does…. well, you figure that out before you push 1.1.
I’ve really wished that there was some way for projects to include a ‘suggested donation’ that could say, by the # of times the library was referenced as a % of code, a flat fee per estimated user (or per minute of seat time per user or something), or based on the # of times the library was called as part of automated testing.
Then Node (or whatever) could spit out a table saying, you don’t have to pay anyone anything, but this is what the developers of each of these libraries you’ve used have suggested based on the following criteria; consider that if you can. 99.9% wouldn’t, but I mean, if it turns out Facebook is using your library for something user-facing, it’s in their best interests to make sure the code is maintained.
Comment 1 reply
Came here to say this. Breaking changes happen even in core libraries that do one basic thing, and even a pretty careful developer can’t always roadmap and predict when those will need to happen (think the "Y2K22" bug that hit Outlook and a few other places – that forces
a change either in the way time is counted, or at least the type of variable used to store time).
If your project isn’t being updated frequently, PIN VERSIONS to whatever you tested on so that even if only 5 people need . If your project is being updated frequently, PIN VERSIONS since updates to those libraries can happen in the middle of the night and your app might break for your users until you get it fixed.