Hi again! I've been experimenting, how do you like the images attached (or some variation of them)?
(`assert.equal` is legacy, `fs.exists` is deprecated, and `fs.Utf8Stream` is experimental)
@aviv.sh
Loves animals. Tolerates computers. βοΈ @openjsf.org JavaScriptLandia recipient π https://aviv.sh πΎ https://github.com/avivkeller βοΈ me@aviv.sh π https://x.com/@aviv_keller π οΈ Security Researcher π» Node.js Collaborator π¦ Webpack Security
Hi again! I've been experimenting, how do you like the images attached (or some variation of them)?
(`assert.equal` is legacy, `fs.exists` is deprecated, and `fs.Utf8Stream` is experimental)
βOnce itβs readyβ could be quite a while xD
Currently, the colors match the stability alert boxes, which are
Green: Stable (empty on sidebar)
Orange: Experimental
Red: Deprecated
Blue: Legacy
I do however like the idea of a strike through for these deprecated / legacy APIs (just, we also need to differentiate them from one another)
Thanks!
Hey there! We also have βLearnβ guides on our website for more beginner-friendly content.
We can definitely work on the ordering and layout of the learn guides, but at the moment, the docs are labeled alphabetically for consistency with previous versions.
Perhaps, in the future, thisβll change.
Thanks for the feedback! I believe, in the current design, itβs at the bottom of the page, but even so, thatβs definitely a decent length to scroll just to reach the ToC, so a better solution can definitely be reached.
Hi! It looks like your view the legacy documentation page. While we appreciate the feedback, and will definitely look into it, we would especially appreciate feedback on our new design.
The link is in my original post.
Thank you!
Okay, Iβm ready for 2026
Donβt push to production on Christmas Eve!
There is a direct correlation between my interest in a show and the speed at which spoilers appear on my feed
Hey @nodejs.org community!
Weβre looking for your feedback on our beta documentation layout!
π nodejs-api-docs-tooling.vercel.app
Share your thoughts by replying to this post, or open an issue:
π github.com/nodejs/doc-k...
The docs are built for you, so your input truly makes a difference π
Reliability is our top priority. We have declared "Code Orange: Fail Small" to focus our engineering efforts on a single goal: ensuring the causes of past outages are fundamentally eliminated. Here is how we are building a more resilient network for the future. https://cfl.re/4pOLIlC
Iβm proud to continue my @nodejs.org journey as a newly onboarded Core Collaborator!
Why is @github.com planning to charge for self-hosted runners?
Weβre providing the infrastructure ourselvesβ¦ why should we have to pay GitHub to use it?
At that point, itβs cheaper to just hook up an external CI pipeline.
JavaScriptLandia OUTSTANDING CONTRIBUTION FROM A NEW ARRIVAL AWARD 2025 presented to AVIV KELLER
π
9 years ago from today @rich-harris.dev made the first commit to @svelte.dev π°
github.com/sveltejs/sve...
The Node.js Website Team: Faster than AWSβ’οΈ
Hey, THANK YOU JSConf! π
To everyone who shared their ideas, sang way too hard at karaoke, and made the hallway track feel like a family reunion... youβre the best.
That's a wrap π
I was there π
Had a great time at @jsconf.bsky.social and the @nodejs.org #CollabSummit, looking forward to all the cool things planned!
I know which exercise that was π!
π«Ά
Iβm beyond thrilled to be the recipient of this yearβs #JavaScriptLandia βOutstanding Contribution from a New Arrivalβ award! This award is truly a testament to the fact that anyone, with faith and effort, can make a meaningful impact in #OpenSource.
Thank you,
@openjsf.org
.@nodejs.org now shows @typescriptlang.org definitions on hover!
Check it out at nodejs.org!
See yβall next week for @jsconf.bsky.social!
That is a learn article
Feel free to open issues regarding security policy in our repository, linked in my original post :-)
At @nodejs.org, we are experimenting with type-checked code snippets, WDYT?
Excited to join Webpackβs new Security Working Group!
github.com/webpack/secu...