GitHub - watson/codeowners-audit: Scans a repo's CODEOWNERS coverage, generates an interactive HTML gap report, and can fail in CI or from the CLI when files are not covered. Scans a repo's CODEOWNERS coverage, generates an interactive HTML gap report, and can fail in CI or from the CLI when files are not covered. - watson/codeowners-audit

Here's an example report for the Node.js core repo: watson.github.io/codeowners-a...

Try it out today by running this command in your project:

npx codeowners-audit

See more at: github.com/watson/codeo...

CODEOWNERS Gap Report for the Node.js core repo

I built a small tool after running into a problem I think a lot large repos have!

GitHub gives almost no insights in CODEOWNERS files:

How much of this repo is actually covered?
Which directories have the biggest ownership gaps?
Which specific files have no matching owner rule?

👉 🧵

What's going on with the `next` package and npm servers today?

All day our CI randomly gets these errors. But for some reason only for `next`. Any other npm package works fine. Re-run it a few times and the error goes away 🤔

status.npmjs.org is all green, but that page has never been reliable 🤷

Blue Sky | 2025 Daily, Weekly, and Monthly Planners The Blue Sky planner is the solution to your planning needs. Select from our assortment of 2025 daily, weekly, and monthly planners for the new year!

I would love to see the visitor stats for bluesky.com these days

I was using Copilot today to write a bash script and I had an array of host names. It suggested this code - even added a nice copyright. Seems to come from this Node.js book: www.scribd.com/document/685...

Originally class was just synthetic sugar for what could be achieved with classic prototypical inheritance. But you’re right, as time has moved on the classes the feature set split

_rawDebug FTW 😂 I often find myself using that especially at times where I get weird sync/async behavior and can’t correlate the output in a multi threaded environment… I haven’t verified but it feels that sometimes console.log goes through extra async layers… maybe in the os

The link to the issue in the release notes is incorrect. Would love to read more about if there’s limits to these groups (eg there has to be more then x with same props to form a group, or max number of properties in an object and so on). Does anyone have more information?

Heap snapshot in Chrome Devtools with all objects in one row

Heap snapshot in Chrome Devtools with all objects in separate rows

This is a huge improvement to heap inspection inside Chrome DevTools 👍

Seth Brenith at Microsoft gave many anonymous object literals top-level names (using their properties) to stop them getting unhelpfully categorized under "Object".

Pics show before & after.

developer.chrome.com/blog/new-in-...

On my way home from NodeConf and the Node.js Collaboration Summit in Dublin. Great to see so many old and new friends! 😊 And wow, I finally posted on this app 🦋