11 replies

1. Zach Leatherman Mastodon 1 min later

   anyway node.js just bails out silently when this happens so it’s decidedly not a fun issue to track down 😭

   1. Eric Portis Mastodon 1 hr later

      @zachleat this is why we can’t have container queries

      1. Zach Leatherman Mastodon 2 hr later

         @eeeps haha *exactly*

         we must protect CSS developers

2. Zach Leatherman Bluesky 5 min later

   anyway node.js just bails out silently when this happens so it’s decidedly not a fun issue to track down 😭

   1. Private reply Bluesky 7 min later
      1. Zach Leatherman Bluesky 13 min later

         well wait just one minute I love Node.js

3. Luis Crespo Bluesky 29 min later

   You can do that with some node.js JavaScript code? Can you please share an example?

   1. Zach Leatherman Bluesky 1 hr later

      Not at the computer right now but it was two p-queue instances fighting with each other

      1. Zach Leatherman Bluesky 1 hr later

         (With async callbacks)

4. Erika Bluesky 9 hr later

   oh would love to know more about how this can happen! I happens to be juggling queues like that these days at work and I now worry I could run into this

   1. Zach Leatherman Bluesky 10 hr later

      I think the biggest takeaway for me is to make sure the queues don’t have circular references! Promise A waiting for Promise B waiting for Promise A is bad news 🫣🫣🫣