#nodejs

@arad@mastodon.projetretro.io · May 21, 2026

#introduction So this is it, right ? The way we say "hello world" here. So let's get the deed done. I'm arad, tired of the high mileage shit I was serve upon the internet buffet so I went to the local familly managed shit dinner. My average day is wondering how modern software became that bad with the massive amounts of money invested in those over the years. My nemesis will be #nodejs and #npm but python and #rust are pretty high on that list too. If you"re offended by what I'm saying, congrats, indeed I wrote it especially with you in mind and also you may suffer from "Main Protagonist Syndrom". Anyway., see you.

0

Frontend Dogma

@frontenddogma@mas.to · May 06, 2026

Node.js 26.0.0 (Current), by @rafaelgss.dev (@nodejs@social.lfx.dev): https://nodejs.org/en/blog/release/v26.0.0 #releasenotes #nodejs

2

0

3

0

Node.js Release Watcher

@nodejs_release_watcher@mastodon.kodesumber.com · May 05, 2026

"There is a new release of node.js. Happy updating and coding." # 2026-05-05, Version 26.0.0 (Current), @RafaelGSS We're excited to announce the release of Node.js 26! Highlights include the Temporal API enabled by default, updates to the V8 JavaScript engine to 14.6, Undici to 8.0, and several important deprecations and removals as we continue to modernize the... https://github.com/nodejs/node/releases/tag/v26.0.0 #nodejs #javascript

0

Axios Release Watcher

@axios_release_watcher@mastodon.kodesumber.com · May 04, 2026

"There is a new release of axios. Don't forget to run npm i axios@latest." # v0.32.0 v0.32.0 — May 4, 2026 This release backports a comprehensive set of security and hardening fixes from the v1.x branch into v0.x, covering prototype-pollution protections, default error redaction, stricter proxy/cookie/socket handling, and one... https://github.com/axios/axios/releases/tag/v0.32.0 #axios #nodejs

0

Lobsters

@lobsters@mastodon.social · Apr 27, 2026

Running the Gauntlet: a tiny nodejs test runner by @robey@messydesk.social https://lobste.rs/s/mytuvk #show #nodejs #testing https://robey.lag.net/2026/04/26/running-gauntlet.html

0

1

0

Aral Balkan

@aral@mastodon.ar.al · Feb 27, 2026

🥳 New Kitten Release This one fixes a bug that you would have encountered had you had an asynchronous component (component with asynchronous render method) nested more than one-level deep within synchronous components. (Kitten’s html renderer transparently supports both synchronous and asynchronous render methods.) So, this (taken from my unit test), for example, works correctly now: ```js class AsynchronousOtherName extends KittenComponent { async html () { await new Promise(resolve => setTimeout(resolve, 10)) return kitten.html`Balkan` } } class SynchronousName extends KittenComponent { /* NOT async */ html () { return kitten.html`Aral <${AsynchronousOtherName.connectedTo(this)} />` } } class SynchronousTemplate extends KittenComponent { html ({ SLOT }) { return kitten.html`[Before slot]${SLOT}[After slot]` } } class MyPage extends KittenPage { html () { return kitten.html` <${SynchronousTemplate.connectedTo(this)}> This should render all at once after a short delay.

Hello, <${SynchronousName.connectedTo(this)} />

3

1

3

0