HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sindresorhus
user-home
JavaScript2016–2016
sindresorhus / user-home · Archived

user-home

Get the path to the user home directory

2Distinct people
2Mentions
0Explicit recommenders
156GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Get the path to the user home directory

GitHub

Where it is used

No documented product use has been verified yet.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 hour2 dated mentions

Observed mentions: 2016-03-23 18:23:32 UTC to 2016-03-23 20:05:28 UTC.

012016-03-23 18:00:00 UTC to 2016-03-23 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 23, 18:002016-03-23 19:00:00 UTC to 2016-03-23 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 23, 19:002016-03-23 20:00:00 UTC to 2016-03-23 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 23, 20:00

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
Mar 23, 18:002016-03-23 18:00:00 UTC2016-03-23 19:00:00 UTC101
Mar 23, 19:002016-03-23 19:00:00 UTC2016-03-23 20:00:00 UTC000
Mar 23, 20:002016-03-23 20:00:00 UTC2016-03-23 21:00:00 UTC101

What Hacker News says

1 sources
I agree that there is a definite cost of dependencies. I don't agree with the implication that these small modules are frivolous - doing one thing and doing it well is a time honored Unix principle. It saves developers from having to roll their own dependency, and gives them free wins if the package is well maintained and widely used. Edge cases are often identified and accounted for, even if the responsibility of the package is tiny. The example you gave was a poor choice - read further down https://github.com/sindresorhus/user-home#why-not-just-use-t.... It exists to avoid exactly the problem that sparked the conversation around npm today.
In Alert: NPM modules hijacked

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.