Geoffrey Booth

> @joyeecheung Could you clarify what UI element you refer to? I must have never noticed that. Perhaps Joyee means the box above the merge button, that lists all the...

Why do we need this label at all, though? We require contributors to land PRs via `git node` or `commit-queue`, right, and both of those check that CI has run...

> It was explained above [#1044 (comment)](https://github.com/nodejs/TSC/issues/1044#issuecomment-867073408) though I’ll say I’ve never seen anyone overriding the ncu judgement.. Okay, so if the only goal we need to preserve is the...

So can we just invert it? CI is assumed to be required by default, and the `ci-unnecessary` label can be added if we want to override the script to tell...

This is resolved by 20.6.0 whenever it ships.

FYI https://github.com/nodejs/node/pull/50669 will backport the changes on 20 (`register`, etc.) to 18.x.

> Importing YAML directly into a node.js program seems like it could be pretty useful. How far away are we from such a reality? It’s unlikely to be ever supported...

> UPDATE: [official documentation](https://nodejs.org/api/esm.html#esm_loaders) is probably where I should start… Yes, the official docs should be all you need. The “transpiler loader” example is the pattern you’d want to follow;...

> Regarding augmenting functionality, could these helpers be implemented in ESM? If so, then couldn’t loaders be used to customise their dependencies? At the moment, at least, all internal code...

> couldn’t node expose the a `DefaultLoader` prototype it uses itself to instantiate a loader object No, because then the entire class becomes a public API surface and we could...