TL;DR
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
A developer writing on Oct. 3 said they had returned to Node.js after using Deno for years, following work on a SvelteKit client project and a static-site-generator migration. They reported that the migration required few changes and that builds ran 15% faster in their test, while also citing problems with Deno tools and services. The account is one developer’s experience, not a broader performance comparison.
A developer has described returning to Node.js from Deno after using Node on a SvelteKit client project and migrating a static site generator, reporting that the conversion required few code changes and produced 15% faster builds in their test. The account, published Oct. 3 on dbushell.com, is a single developer’s experience rather than an independent benchmark or evidence of a general Node performance advantage.
The author said Node.js had become more capable since their earlier experience with it, citing support for modern ECMAScript features and updated APIs. In the static site generator, the required changes included replacing Deno’s file-system API with Node’s node:fs and replacing Deno.serve with Hono’s Node adapter, which uses node:http. The author also switched Deno’s path library for Node’s node:path.
In that migration, the author reported that builds became 15% faster, despite the code still favoring Deno-style conventions. The post does not describe the test conditions, hardware, workload, or repeated measurements, so the figure should be read as a result from that project, not a controlled comparison between the runtimes.
The author also discussed package management and TypeScript. They chose Fast Node Manager to manage Node versions and PNPM for package installation, configuring a minimum release age of one day and a trust policy. They noted that Node’s documentation restricts stripping TypeScript types in files under node_modules, so they used a bundling tool for their packages. These are the author’s setup choices and views, not recommendations established by the report.
A Lower-Friction Move to Node
The account reflects a practical choice developers make when selecting a JavaScript runtime: whether a familiar tool still meets project needs, and how much work it takes to move. The author’s migration suggests that, for this particular static-site project, prior differences between Deno and Node did not prevent a small conversion. Their reported 15% build-time improvement may interest developers weighing options, but does not establish which runtime is faster for other applications.
The post also illustrates that runtime selection involves more than execution speed. The author raised concerns about dependency security, package provenance, TypeScript publishing and the reliability of developer tooling. Those issues can affect maintenance and release workflows, but the post does not provide a comparative security assessment of Deno and Node or verify that one package manager is safer overall.
As an affiliate, we earn on qualifying purchases.
From Deno Use to Node Migration
The author said Deno had been their preferred runtime for a long period, but recent work brought them back to Node. They described using Node heavily during the month before the post, then testing the migration on their own static site generator. The account therefore combines observations from a client project with a specific conversion exercise, rather than a formal review of either runtime.
The report identifies several frustrations behind the decision: broken ZSH integration, repeated HTTP 429 responses from JSR, and bugs the author said affected concurrent HTTP requests. The author also criticized changes in Deno’s company and product direction. Those broader judgments are opinions in the post; the runtime complaints are the author’s reported experience and are not accompanied by issue links or independent verification.
“Node got a glow-up, wow!”
— The author, dbushell.com
As an affiliate, we earn on qualifying purchases.
Limits of the Reported Results
The post does not provide enough detail to reproduce or generalize the 15% build-time result. It does not state the machines, build settings, number of runs, or whether the before-and-after environments were otherwise identical. It is also unclear whether other projects using Deno would require similarly few changes to move to Node.
The author’s reports of Deno tooling and service problems are not independently documented in the supplied material. The post also does not compare the security properties of Node, Deno, NPM, or PNPM. Its criticism of Deno’s company direction and the author’s comments about package ecosystems should be understood as personal assessment, not verified industry-wide conclusions.
As an affiliate, we earn on qualifying purchases.
Further Node Tuning Planned
The author said they may explore additional Node built-in APIs to see whether the migrated project can be improved further. They had already replaced the path-library import and made the minimum changes they considered necessary for the migration.
No broader follow-up study, independent benchmark, or response from Deno was included in the report. The immediate next step described is continued work on the author’s own Node-based site generator; whether the reported performance difference persists under further testing remains unknown.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did the developer switch from and to?
The author moved a static site generator from Deno to Node.js after also using Node on a SvelteKit client project.
Did the migration make builds faster?
The author reported 15% faster builds in their project after migration. The post does not give testing details, so the result cannot be treated as a general Node-versus-Deno benchmark.
What changes were needed for the site generator?
The author replaced Deno’s file-system API with node:fs, changed Deno.serve to Hono’s Node adapter, and switched from Deno’s path library to node:path.
Why did the author leave Deno?
The author cited reported problems with ZSH integration, JSR rate limits, and concurrent HTTP requests, along with dissatisfaction with Deno’s product direction. These are the author’s stated reasons and are not independently verified in the report.
Does the report show that Node is better than Deno?
No. It describes one developer’s experience and one project migration. It does not provide controlled benchmarks or evidence that Node will be a better fit or faster for other projects.
Source: hn
Evergreen bestsellers Picks
bestsellers
As an affiliate, we earn on qualifying purchases.
