March 26, 2024

Lots of Node.js news in this issue! We have added sections to help you skip it in case you are not interested.

Axel & Jowe

Node.js news

Node.js: The Documentary | An origin story [63-min. video]

www.youtube.com @nodejs@social.lfx.dev github.com/honeypotio

“Join us as we delve into the origins of Node.js, meet some of its earliest contributors and explore the complicated dynamics between corporations using open source technologies and the dedicated community members who fuel their progress. Featuring interviews with Ryan Dahl (creator of Node.js), Isaac Schlueter (creator of npm) and more.”

The redesigned nodejs.org is live

social.lfx.dev @nodejs@social.lfx.dev

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.

require(esm) in Node.js

joyeecheung.github.io github.com/joyeecheung

“Recently I landed experimental support for require()-ing synchronous ES modules in Node.js, a feature that has been long overdue. In the pull request, I commented with my understanding about why it did not happen sooner before this pull request in 2024. This post expands on that comment a bit more.”

JAMstacked

cfe.dev Sponsor

If you're interested in full stack development using JavaScript, also check out the Jamstacked newsletter. It publishes every two weeks including the top links, with context, for web developers curated by @remotesynth.

Three new built-in Node.js features

www.raymondcamden.com @raymondcamden@mastodon.social

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

Node.js Technical Steering Committee confirms: no intention to remove npm from distribution

socket.dev @sarahgooding@fosstodon.org @SocketSecurity@fosstodon.org

Other topics

vlt technology Inc. unveils team & investors and hints at mission: improving JavaScript packaging ecosystem

blog.vlt.sh github.com/isaacs github.com/darcyclarke github.com/ruyadorno github.com/vltpkg

Key members of the team:

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.”

Igalia joins Open Web Docs Governing Committee

openwebdocs.org @floscholz@front-end.social @openwebdocs@front-end.social @igalia@floss.social

“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.”

Turborepo 1.13: new terminal UI and more

turbo.build github.com/gsoltis github.com/chris-olszewski github.com/vercel

Highlights (quoting the blog post):
  • 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

Kuto: ship JavaScript updates incrementally

samthor.au @samthor@mastodon.social

"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."

Markcheck: test Markdown code blocks with JavaScript and other languages

github.com @rauschma@fosstodon.org

‍

What do you think of this issue?

If you have any comments or feedback, just reply to this email!
‍

This email was sent to {{ email | default }}. You can unsubscribe from this list here or update your preferences.

‍