Conversation

Notices

1. Embed this notice
   Aral Balkan (aral@mastodon.ar.al)'s status on Wednesday, 29-May-2024 23:59:19 JST Aral Balkan

   A little detail in the latest #Kitten:

   I find Node.js deprecation warnings hit that sweet spot between jarring enough to be annoying and not informative enough to be useful. So, in Kitten, the first time a deprecation warning is encountered, you a see message telling you there are deprecation warnings.

   If you care, you can open the internactive shell and look at the contents of kitten.deprecationWarnings, which will show you full details including the stack trace.

   :kitten:💕

   #SmallWeb #design

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

     in reply to

     • thylacoleo

     @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.)

   • Embed this notice
     thylacoleo (thylacoleo@mas.to)'s status on Thursday, 30-May-2024 00:23:35 JST thylacoleo

     in reply to

     @aral

     People diss on PHP, but we had all kinds of warnings there.

   • Embed this notice
     thylacoleo (thylacoleo@mas.to)'s status on Thursday, 30-May-2024 01:31:25 JST thylacoleo

     in reply to

     @aral

     Apologies. I let out my inner redditor for a moment.

   • Embed this notice
     Aral Balkan (aral@mastodon.ar.al)'s status on Thursday, 30-May-2024 01:31:25 JST Aral Balkan

     in reply to

     • thylacoleo

     @thylacoleo :P