os-paths

Determine common OS/platform paths (home, temp, ...)

Installation (CJS/ESM/TypeScript)

npm install os-paths
# or... `npm install github:rivy/js.os-paths`
# or... `npm install "https://cdn.jsdelivr.net/gh/rivy/js.os-paths@latest/dist/os-paths.tgz"`

Usage

CommonJS (CJS)

const osPaths = require('os-paths');
const home = osPaths.home();
const temp = osPaths.temp();

ECMAScript (ESM)/TypeScript

import osPaths from 'os-paths';
const home = osPaths.home();
const temp = osPaths.temp();

Deno

import osPaths from 'https://deno.land/x/os_paths@v6.1.0/src/mod.deno.ts';
//or (via CDN, with semver support)...
//import osPaths from 'https://cdn.jsdelivr.net/gh/rivy/js.os-paths@6/src/mod.deno.ts';
const home = osPaths.home();
const temp = osPaths.temp();

API

Construction/Initialization

OSPaths()

const osPaths = require('os-paths'); // CJS
//or...
//import osPaths from 'os-paths'; // ESM/TypeScript
//import osPaths from 'https://deno.land/x/os_paths@v6.1.0/src/mod.deno.ts'; // Deno

When importing this module, the object returned is a function object, OSPaths, augmented with attached methods. Additional OSPaths objects may be constructed by direct call of the imported OSPaths object (eg, const p = osPaths()) or by using new (eg, const p = new osPaths()). Notably, since the OSPaths object contains no instance state, all OSPaths objects will be functionally identical.

Methods

All methods return simple, platform-specific, and platform-compatible path strings which are normalized and have no trailing path separators.

The returned path strings are not guaranteed to already exist on the file system. So, the user is responsible for directory construction, if/when needed. However, since all of these are standard OS directories, they should all exist without the need for user intervention.

If/when necessary, make-dir or mkdirp can be used to create the directories.

osPaths.home(): string | undefined

• Returns the path string of the user's home directory (or undefined if the user's home directory is not resolvable).

console.log(osPaths.home());
//(*nix) => '/home/rivy
//(windows) =>  'C:\Users\rivy'

osPaths.temp(): string

• Returns the path string of the system's default directory for temporary files.

temp() will always return a non-empty path string (as sanely as possible).

console.log(osPaths.temp());
//(*nix) => '/tmp'
//(windows) =>  'C:\Users\rivy\AppData\Local\Temp'

Supported Platforms

NodeJS

Requirements

NodeJS >= 4.0[^*]

[^*]: With the conversion to a TypeScript-based project, due to tooling constraints, building and testing are more difficult and more limited on Node platforms earlier than NodeJS-v10. However, the generated CommonJS/UMD project code is fully tested (for NodeJS-v10+) and continues to be compatible with NodeJS-v4+.

CommonJS modules (CJS; *.js and *.cjs)

CJS is the basic supported output (with support for NodeJS versions as early as NodeJS-v4).

const osPaths = require('os-paths');

console.log(osPaths.home());
console.log(osPaths.temp());

ECMAScript modules (ESM; *.mjs)

• Requires v6.0+.

OSPaths fully supports ESM imports.

import osPaths from 'os-paths';

console.log(osPaths.home());
console.log(osPaths.temp());

TypeScript (*.ts)

• Requires v5.0+.

As of v5.0+, OSPaths has been converted to a TypeScript-based module. As a consequence, TypeScript type definitions are automatically generated, bundled, and exported by the module.

Deno

• Requires v6.0+.

OSPaths also fully supports use by Deno.

import osPaths from 'https://cdn.jsdelivr.net/gh/rivy/js.os-paths@latest/src/mod.deno.ts';
//or (via CDN, with semver support)...
//import osPaths from 'https://cdn.jsdelivr.net/gh/rivy/js.os-paths@6/src/mod.deno.ts';

console.log(osPaths.home());
console.log(osPaths.temp());

Building and Contributing

Build requirements

• NodeJS >= 10.14
• a JavaScript package/project manager (npm or yarn)

optional

• git-changelog ... enables changelog automation

Build/test

npm install-test

Project development scripts

> npm run help
...
usage: `npm run TARGET` or `npx run-s TARGET [TARGET..]`

TARGETs:

build               build/compile package
clean               remove build artifacts
coverage            calculate and display (or send) code coverage [alias: 'cov']
fix                 fix package issues (automated/non-interactive)
fix:lint            fix ESLint issues
fix:style           fix Prettier formatting issues
help                display help
lint                check for package code 'lint'
lint:commits        check for commit flaws (using `commitlint` and `cspell`)
lint:lint           check for code 'lint' (using `eslint`)
lint:markdown       check for markdown errors (using `remark`)
lint:spell          check for spelling errors (using `cspell`)
lint:style          check for format imperfections (using `prettier`)
realclean           remove all generated files
rebuild             clean and (re-)build project
retest              clean and (re-)test project
reset:hard          remove *all* generated files and reinstall dependencies
show:deps           show package dependencies
test                test package
test:code           test package code
test:types          test for type declaration errors (using `tsd`)
update              update/prepare for distribution
update:changelog    update CHANGELOG (using `git changelog ...`)
update:dist         update distribution content

Contributions

Contributions are welcome.

Any pull requests should be based off of the default branch (master). And, whenever possible, please include tests for any new code, ensuring that local (via npm test) and remote CI testing passes.

By contributing to the project, you are agreeing to provide your contributions under the same license as the project itself.

Related

• xdg-app-paths ... easy XDG for applications
• xdg-portable ... XDG Base Directory paths (cross-platform)

License

MIT © Roy Ivy III