Node.js documentary; nodejs.org redesign; require(esm) in Node.js; new built-in Node.js features;

Highlights of the new website (quoting the Mastodon post):

• Fresh look
• Comprehensive search
• New learning resources
• APIs & downloads unchanged
• Improved contributor DX

If you want to read more about the history of the redesign and the technology that is used, check out “Diving into the Node.js website redesign” by Brian Muenzenmeyer.

• Watch and reload on change
• Loading environment variables
• Colorful output

Key members of the team:

• Isaac Z. Schlueter: creator of npm
• Darcy Clarke: previously worked at npm Inc.
• Ruy Adorno: previously worked at npm Inc.

Their mission: “We care deeply about developer platforms & tooling, which is why we've spent so much time in this space. However, the packaging ecosystem has stagnated & so there is a wealth of opportunity to innovate. Our mission has always been to improve the developer experience, and we're thrilled to be working together on it again.”

“Open Web Docs is excited to welcome Igalia to our Governing Committee, joining Google and Microsoft Edge. The Governing Committee administers OWD’s financial sponsorships, made via Open Collective, and explores strategic partnerships and needs for web documentation projects.”

“The Governing Committee is composed of organizations sponsoring at the Platinum level, elected representatives from the Gold membership level, individual advisory members, and OWD’s Director.”

• New terminal UI [experimental]: Interact with your tasks locally in an enhanced terminal experience
• Enable the fastest defaults: Make your local development environment faster with turbo scan
• CI logging improvements: Support for four major providers and automatic unfurling of errored tasks
• Enhanced prune support: Bug fixes and improved stability for turbo prune

"Roughly, Kuto splits web app bundles into:

• a “corpus” part with side-effect free code which can be cached for a long time
• a “main” part with the remaining code

The main part changes with each update. If the corpus part changes:

• Old functionality that’s not needed anymore: This code remains as junk in the old corpus (which is usually still cached).
• New functionality: Is put into a new, additional corpus file. The article explains how Kuto handles the fragmentation caused by creating new corpus files.

Why do this? Updates get smaller and can be loaded faster because they use what’s already cached locally."