userhome
npmv1.0.1A cross-platform path to the user's home
Adopt with care
userhome is usable, with caveats. Last published 703 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- CMaintenance: grade C, Fair — worth a look.
Last published 703 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 3.3 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding userhome to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >= 0.8.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the userhome README.
var userhome = require('userhome');
console.log(userhome('.bashrc'));
// /Users/shama/.bashrc
console.log(userhome('test', 'sub', 'file'));
// /Users/shama/test/sub/file
console.log(userhome());
// C:\Users\shamauserhome vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| userhomethis page | 0 | 1 | MIT | 1 year ago |
| tildify | 0 | 1 | MIT | 1 day ago |
| env-paths | 0 | 2 | MIT | 1 day ago |
| path-key | 244.9M | 1 | MIT | 1 day ago |
| @jridgewell/resolve-uri | 166.3M | 1 | MIT | 1 day ago |
| normalize-path | 72.6M | 1 | MIT | 1 day ago |
Dependencies
Declared by userhome v1.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (1)
Used by
Popular packages that depend on userhome.
Relationship graph
Dependencies (left) and dependents (right) of userhome.
Frequently installed together
Release history
No releases in the last two years, typically about 3667 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.1latest | 1 year ago | 3.3 KB | MIT |
| 1.0.0 | 12 years ago | — | MIT |
| 0.1.0 | 13 years ago | — | MIT |
Overview
userhome is an npm package that a cross-platform path to the user's home. It has 1 known dependents in the graph. The latest version is 1.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a cross-platform path to the user's home and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (1 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use userhome?
userhome is usable, with caveats. Last published 703 days ago.
How do I install userhome?
Run `npm install userhome` to add userhome to your npm project.
What license is userhome released under?
userhome is distributed under the MIT license.
How popular is userhome?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on userhome.
Is userhome still maintained?
The most recent release of userhome (v1.0.1) was published 1 year ago.
Does userhome run install scripts?
No. userhome does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.