Benjamin Gruenbaum

To not stall-block this, I've added tsc-agenda and messaged the TSC about this. If we reach consensus before the meeting I'll remove the TSC agenda label. What I believe is...

> My preference would be to just emit a warning to the console if this happens but still allow it to continue working. Do you have a preference to the...

The TSC has not reached consensus and internal discussions made the point: > Someone should answer the question “why hasn’t the browser started warning on it yet?” Opinions ranged from...

> First let's answer Benjaming's question: Hey, not my question it was raised by another TSC member :) The relevant places for where these conversions happen isn't the timers spec...

It looks like we are amending the process to allow this (so the runtime warning PR should eventually land and not this one): https://github.com/nodejs/node/pull/53513 48h have passed and it has...

@RedYetiDev blob is a web standard, this method is added to the spec, we should definitely implement it (as experimental and remove experimental status when it lands).

Implementing _before_ the spec lands is almost always a good idea since it's literally our last realistic chance to request changes or provide feedback when we see an API is...

Node handles this for Blob and undici handles it for request/response

That's not a bug afaik debugging inside core isn't supported. The user can use the userland `readable-stream` (slightly older though) and break there https://www.npmjs.com/package/readable-stream :]

(Or they can build core from source and put a literal `debugger` that worked for me in the past (and there is --inspect-brk-node but I don't think that'd help)