HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
denoland
deno
Rust2018–2026
denoland / deno

deno

A modern runtime for JavaScript and TypeScript.

161Distinct people
202Mentions
1Explicit recommenders
108.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A modern runtime for JavaScript and TypeScript.

GitHub

Where it is used

  • Netlify — Netlify used Deno Subhosting to build and ship its edge functions product within weeks, choosing it over building their own solution on AWS Lambda. Source

What people are saying

I love Deno and I use this, but I really wish they would fix this dumb bug: https://github.com/denoland/deno/issues/16466

IshKebab used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year202 dated mentions

Observed mentions: 2018-08-23 15:35:35 UTC to 2026-10-16 06:53:01 UTC.

010203040502018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 16 mentions; 4 submissions, 12 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 45 mentions; 18 submissions, 27 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 30 mentions; 4 submissions, 26 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 33 mentions; 4 submissions, 29 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 30 mentions; 1 submissions, 29 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 18 mentions; 0 submissions, 18 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC16412
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC817
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC451827
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC30426
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC33429
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC30129
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC918
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC18018
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC13112

What Hacker News says

8 sources
This does not necessarily invalidate your wider points, but just FYI: > It does not interop with JavaScript. Hm, this depends on your definition of "interop". My JavaScript and TypeScript are languages that exchange information. The execution model ultimately involves JavaScript when I use tsc, but ultimately it also includes an interpreter. My user-space syntax doesn't care. > There is no such thing as a TypeScript runtime engine. Not being glib, just a heaps up: https://github.com/denoland/deno
In TypeScript 3.7
TypeScript is very easy to use with Node. You can also use the debugger in WebStorm with it just fine, and you'll be stepping through your TS code instead of your generated JS code. The problem is really the Node ecosystem, which is a mess and a circus of security issues. Deno[1] may fix most of JS/Node's problems eventually. For now, if you want a type system that's comparable to TS with a great ecosystem, the best you can get is either F# or Kotlin. If you're not a fan of ML, then you might want to start with Kotlin. 1. https://github.com/denoland/deno
In When to Use TypeScript – A Detailed Guide Through Common Scenarios

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.