HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nodejs
node
JavaScript2014–2026
nodejs / node

node

Node.js JavaScript runtime ✨🐢🚀✨

Web DevelopmentSystems & InfrastructureLanguages & CompilersMobile & Desktop
Explore on GitHubRead Hacker News discussions
376Distinct people
482Mentions
1Explicit recommenders
123.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Node.js JavaScript runtime ✨🐢🚀✨

GitHub

Where it is used

  • weather.com — weather.com uses Node.js to power its website. This is the runtime behind their public weather.com site. Source

What people are saying

Expect a blog post shortly, but from v8 we get these language changes: - await/async behind flag (already covered in thread) - Exponentiation operator: > console.log(60**2*24);…

jbergstroem 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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 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 year482 dated mentions

Observed mentions: 2014-11-28 03:40:25 UTC to 2026-11-01 13:22:11 UTC.

0204060801002014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 96 mentions; 41 submissions, 55 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 68 mentions; 23 submissions, 45 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 66 mentions; 25 submissions, 41 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 31 mentions; 10 submissions, 21 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 19 mentions; 11 submissions, 8 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 22 mentions; 13 submissions, 9 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 20 mentions; 5 submissions, 15 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 27 mentions; 7 submissions, 20 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 32 mentions; 11 submissions, 21 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 39 mentions; 11 submissions, 28 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 17 mentions; 3 submissions, 14 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 31 mentions; 8 submissions, 23 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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC14311
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC964155
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC682345
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC662541
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC311021
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC19118
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC22139
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC20515
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC27720
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC321121
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC391128
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC17314
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC31823

What Hacker News says

66 sources
nikcub·Oct 25, 2017
Not sure if you read that issue because it was closed as it depends on OpenSSL 1.1. Fire up 8.8.0 and you'll find crypto.scrypt is undefined. nodejs will have to get the OpenSSL 1.1 upgrade in as the support period for nodejs 8.x exceeds the support period for OpenSSL 1.0.x First attempt was made here[0] [0] https://github.com/nodejs/node/pull/11828
In Node v8.8.0
Cthulhu_·Oct 5, 2017
I've only dabbled myself, but I can see how that would start; I come from a Java background which forces you to have one module / class per file, but Go doesn't. It's very easy to start hacking up a thing, and it's easier in development to just keep it in one file. Of course, the nature of code is that it grows, so spend enough time there and it'll start growing. If you're familiar with the code (as in, you wrote it yourself), single files shouldn't be a problem. It's not uncommon in other projects either, NodeJS for example has a relatively small number of large files (https://github.com/nodejs/node/blob/master/src/node.cc).
In Show HN: Encrypted VPN in 2k lines of Go
_urga·Sep 26, 2017Submission

Ask HN: Running Node on Linux with RSS More Than 16 GB?

We have noticed that Node's spawn() is not asynchronous on Linux with memory RSS more than 16 GB, blocking the event loop for as much as 2 seconds. The issue comes down to Linux copying the entire RSS each time spawn() is called from the main event loop thread. Moving the call to uv_spawn() to the threadpool would likely fix the issue by not blocking the main event loop thread. If you think you might be affected, there is a short script to reproduce here: https://github.com/nodejs/node/issues/14917#issuecomment-323697188
1 points · Open discussion
_urga·Sep 23, 2017Submission

Ask HN: Anyone running Node on Linux with memory RSS more than 16 GB?

We have noticed that Node's spawn() is not asynchronous on Linux with memory RSS more than 16 GB, blocking the event loop for as much as 2 seconds. The issue comes down to Linux copying the entire RSS each time spawn() is called from the main event loop thread. Moving the uv_spawn() to the threadpool would likely fix the issue by not blocking the main event loop thread. If you think you might be affected, there is a short script to reproduce here: https://github.com/nodejs/node/issues/14917#issuecomment-323697188
2 points · Open discussion
skybrian·Aug 27, 2017
re: "Promises have to be resolved in the next turn of the event loop. This is part of the spec." This seems imprecise? There are multiple queues and the details seem to be implementation-specific [1]. The Promises/A+ specification doesn't seem to specify a particular implementation [2]. The reason this might matter is that if you use promises to do something CPU-intensive without doing I/O, it might be possible to starve the event queue, similar to what happens if you're just writing a loop. On the other hand, the example in the article is waiting on reads, so they'll be delivered through the event queue. Can reading larger chunks at a time and buffering be used to speed that up? [1] https://github.com/nodejs/node/issues/2736#issuecomment-1386... [2] "This can be implemented with either a 'macro-task' mechanism such as setTimeout or setIm
Read the rest
mediate, or with a 'micro-task' mechanism such as MutationObserver or process.nextTick. Since the promise implementation is considered platform code, it may itself contain a task-scheduling queue or 'trampoline' in which the handlers are called."
In Async Iterators: These Promises Are Killing My Performance

Showing the 15 most recent of 66 sources. Enable JavaScript to search and browse every indexed mention.

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.