@on8cb old libs problem
a module should identify all the libs it uses in it’s package.json file, as 'dependencies.
it worked and the authors didn’t know about this.
we deleted the libs as they were removed from distribution (deprecated)… and oops the module still needs them but didn’t say so.
if they had, and created a package.json file (npm init -y) the problem would not have occurred.
apis not working… well nobody wants to drag old stuff along anymore ‘too much work’… so they change whatever they want, too bad for developers or users.
when I worked for IBM my mentor reminded me often that, when u document an API, it lives like that forever. same input produces the same output. you want to ADD stuff ok, it’s a new API… stuff doesn’t break… customers can continue to depend on you…
anyhow…
certs… well they expire… app owners should plan for that… nah, too much work, we’ll deal w it then…