Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 30-May-2024 00:23:34 JST

@thylacoleo Not sure how that’s relevant :) The problem is not lack of warnings. Node has warnings. It’s the layering.

(Deprecation warnings are normally verbose enough to be distracting and mess up the output of your CLI app but they don’t contain a stack trace so you don’t know where they came from and, if you want to see the stack trace, you have to restart Node with a flag. So that’s what this attempts to fix by layering interface with a friendly pointer to the full information.)