Friendship ended with Deno, now Node is my best friend
A developer shares their experience returning to the Node.js runtime after using Deno, highlighting improvements in Node's modern API and TypeScript support. The author also discusses using PNPM and FNM to manage dependencies and versions securely.
Why it matters
This reflects ongoing shifts in the JavaScript ecosystem and developer preferences regarding runtime security and tooling efficiency.
It’s finally time I go crawling back to Node!
I’ve been using Node heavily this month on a SvelteKit client project. When did Node get so good‽ Deno has been my go-to runtime for so long I forgot how to Node. Now I’m back, I find all the ECMAScript † sugar is supported and the old annoying APIs have been replaced or modernised. Most importantly, I never have to see require() .
† Doesn’t seem like that Oracle trademark dispute will see a positive end :(
The official Node docs recommend piping an internet script straight to bash (we never learn) to install NVM to manage Node & NPM. My (ancient) experience with NVM and NPM hasn’t been stellar. I heard Fast Node Manager (FNM) was better to switch Node versions. Obviously I roll bleeding-edge but I have client projects that demand stability.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in