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

14 sources
indutny·Dec 8, 2014
Hello! Just a couple of notes about it, in case if you haven't seen the README.md yet ;) The Caine is a bot to help maintainers of large Open Source projects to off-load the tagging and assigning functions to the issue reporters. The Caine will parse the CONTRIBUTING.md file and get all required info out of it. It will ask the authors of the issues to fill the form to help it tag the issue, and will tag it and assign to one of the maintainers after the proper reply. We are currently using it for: https://github.com/iojs/io.js . Which should (ideally) let us unsubscribe from unfiltered github notifications, and get emails only for the issues that we was assigned to.
In Show HN: Caine – A GitHub bot
scljstcwombat·Dec 6, 2014
Ah yes, Mikeal, whose capability of double-think is so well-developed that he can claim to not understand what "fragmentation" means while at the same time advocating to do precisely that - https://github.com/iojs/io.js/issues/9 I swear Chris Dickinson is the only sane one in this whole mess. Possibly because he's new. Possibly because his employer is the only one involved that's not beholden to VC money and expectations of return.
In IO.js – Evented I/O for V8 javascript
DAddYE·Dec 4, 2014
So for those who wonder: In the TC meeting today we came up with a vision for the first release. First, a few assumptions we've internalized that probably need to be stated for this to make sense. - Node is pretty damn stable already. There are huge companies with it in production, 100K+ modules, etc. It is already far more stable that its pre-1.0 release tag suggests. - Releasing more frequently leads to a more stable product, not a less stable product. - The entire ecosystem uses semver while node uses a confusing even/odd release structure. If people disagree with any of those assumptions then they certainly won't agree with anything the TC determined for the initial release. So, first release of io.js: - January 13th (Fedor's Birthday!) target date. - Will be 1.0-alpha1, with alpha releases con
Read the rest
tinuing until 1.0.0. - Switching to semver. - We will be taking new v8 releases as fast as possible moving forward. - Trying to get to a weekly release cycle. Which version number is incremented each week is determined by the changes and whether or not they are breaking. Again, following semver. Some questions still left open: - Are there any changes other than dep upgrades and fixes required for 1.0? - Is build confident we can have enough automation in place to hit this date. - Is the plan to have the installer install an iojs binary and an alias to node? Source: https://github.com/iojs/io.js/issues/28
In IO.js, a Node fork
oddevan·Dec 4, 2014
Not looking for dirt or anything, but why the fork? What makes this different from Node? (Only clue so far is the "open governance model"; is that in contrast to Joyent maintaining Node?) EDIT: Based on their CONTRIBUTING.md page[1], it looks like this is intended to be a more "community-driven" version of Node. A strike against is that SEVERAL (if not most) links in README.md and CONTRIBUTING.md still reference the joyent/node GitHub project. [1]: https://github.com/iojs/io.js/blob/v0.12/CONTRIBUTING.md
In IO.js, a Node fork

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.