aviv.sh
Animals deserve love, not hate. Be their voice, and stop animal cruelty and abuse.
———
✉️ [email protected]
𝕏 https://x.com/@aviv_keller
🌐 https://aviv.sh
👾 https://github.com/avivkeller
🛠️ Security Researcher + Programmer
💻 @nodejs.org Website Maintainer
203 posts
118 followers
75 following
Regular Contributor
Active Commenter
comment in response to
post
It’s available at github.com/nodejs/nodej...! Feedback is always welcome.
comment in response to
post
When installing Node.js, npm comes bundled as the default package manager. However, our website uses pnpm instead.
comment in response to
post
We’re excited about these changes and the benefits they’ll bring to our developer experience, documentation quality, and overall site performance. Stay tuned for more updates—and as always, feedback is welcome!
comment in response to
post
And just today, we completed adding support for OpenNext deployments!
This unlocks new performance and deployment capabilities for the site.
comment in response to
post
Our UI components are now part of a standalone design system package.
This gives us a single source of truth for styles and behaviors—making development faster and reducing duplication across the site.
comment in response to
post
We’ve begun migrating nodejs/node to our new api-docs-tooling.
This is the first step in a broader effort to modernize and redesign the Node.js documentation experience.
comment in response to
post
First up: we’ve switched our package manager to pnpm!
This change has significantly reduced install times in our CI and development environments, thanks to pnpm’s disk-space optimizations.
comment in response to
post
Yep!
comment in response to
post
We don’t plan to publish, we plan to import directly from the repository.
comment in response to
post
If I’m wrong, we are always looking to improve, and you are more than welcome to submit a PR.
comment in response to
post
We want to avoid requiring pnpm for consumers of the packages in the monorepo (our new docs generator plans to use @node-core/ui-components).
As I understand it, the catalog syntax isn’t npm-friendly, so our tooling would need pnpm, which means, Node Core (the consumer of our generator) would too.
comment in response to
post
Not yet, but we are always looking to improve our codebase
comment in response to
post
I mean, I do study cybersecurity, but if you’re talking specifically about npm security, it’d be wise to also get someone from the npm team to weigh in as well.
comment in response to
post
comment in response to
post
Thanks for your feedback! We are already aware of the table issues (and there’s an assigned issue to fix it), but we’ll look into the toolbar placement issue as well!
comment in response to
post
YOU CAN WHAT?!
comment in response to
post
That’s why I love @astro.build
comment in response to
post
@nodejs.org ❤️ @pnpm.io
comment in response to
post
I can’t wait for that fix 😃
comment in response to
post
Personally, I think the least confusion is:
thatonewebserverlibrarythateverynodejsdevknows
comment in response to
post
Rookie numbers
comment in response to
post
TL;DR: The CVE system is essential for identifying and tracking known cybersecurity vulnerabilities, and its government funding ends within hours
comment in response to
post
We love you GitHub ❤️
comment in response to
post
I’m no expert on time travel, but I’m pretty sure running this code will send us back to the start of the year
comment in response to
post
Holy moly it’s already been a quarter of the year… where has the time gone 🫠