HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nodesource
distributions
Shell2014–2023
nodesource / distributions

distributions

NodeSource Node.js Binary Distributions

Web DevelopmentSystems & InfrastructureLanguages & Compilers
Explore on GitHubRead Hacker News discussions
13Distinct people
13Mentions
0Explicit recommenders
13.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

NodeSource Node.js Binary Distributions

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 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 year13 dated mentions

Observed mentions: 2014-09-05 07:22:42 UTC to 2023-01-31 18:09:55 UTC.

0122014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023

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 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC202
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC220
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211

What Hacker News says

13 sources
mhio·Jan 17, 2022
> Curious how you set that up? Via a DNS server we run, that then answers for local things or forwards requests on to the real world. To do that locally, set up a DNS forwarder like dnsmasq [0] or unbound [1] (or coredns/bind/etc) to respond for the domain you want to wildcard to localhost. Point your OS DNS settings to 127.0.0.1, then configure the forwarder with your regular external DNS servers. The equivalent to `NODE_USE_SYSTEM_CERTS` is a build time option unfortunately. I know the rhel/debian packages do integrate their builds with the system CA's but those packages tend to be ancient. Maybe try the nodesource [2] packaged node.js? The homebrew node formulae [3] looks like it integrates with the brew openssl CA's. [0] https://stackoverflow.com/a/22551303 [1] https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound... [2] https
Read the rest
://github.com/nodesource/distributions [3] https://github.com/Homebrew/homebrew-core/blob/c2579d98415bd...
In Some ways DNS can break
ronjouch·Apr 25, 2020
Better to point people at the official instructions, to give them context about the thing you suggest them to sudocurl: https://github.com/nodesource/distributions#debinstall . Installation nit aside, nodesource is my preferred way to upgrade node on Debian/Ubuntu: 1. It's "just a newer version" of the OS-packaged version! As simple/vanilla as can be. 2. No shell magic making it unclear whether programs running out of the shell will pick up your nvm-managed version of node (most of the time, they won't) 3. And if someday I need to try something on $OLDNODE, it's not much less convenient than nvm: I can just download the deb for $OLDNODE and install it anytime. Then, if you configure your apt cache to keep .debs in /var/cache/apt, switching between versions like nvm does is a matter of just running `sudo dpkg -i /var/cache/apt/node-whateve
Read the rest
r.deb`. (Sure, it's a bit slower than nvm: a few seconds of install rather than milliseconds of updating a symlink in nvm; still I prefer it for reasons 1. and 2.)
In How to Install Node.js for Ubuntu 20.04 LTS?

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.