Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Feb 26, 2024 via pnpm

env-paths 1.0.0

Get paths for storing things like data, config, cache, etc
Package summary
Share
0
issues
1
license
1
MIT
Package created
21 Jun 2016
Version published
10 Jan 2017
Maintainers
1
Total deps
1
Direct deps
0
License
MIT

Issues

0
This package has no issues

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
env-paths@1.0.0
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

0
All Dependencies CSV
β“˜ This is a list of env-paths 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities

Visualizations

Frequently Asked Questions

What does env-paths do?

"env-paths" is a highly useful npm package that locates the correct OS-specific paths for storing data, config, cache, and other similar types of files. This handy tool is particularly useful for developers as it handles the often confusing process of finding the correct storage paths according to the operating system being used. It's also paramount to note that while "env-paths" generates these path strings, it does not create the directories; this is something that the user must manage independently.

How do you use env-paths?

To use "env-paths", you first install it using npm with the command npm install env-paths. After installation, you can import it into your JavaScript programming environment. To generate the paths, call envPaths with the name of your project as an argument. It returns an object containing paths for data, config, etc. Here's a sample code snippet:

import envPaths from 'env-paths';

const paths = envPaths('MyApp');

console.log(paths.data); 
// This might output: '/home/sindresorhus/.local/share/MyApp-nodejs'

console.log(paths.config);
// This might output: '/home/sindresorhus/.config/MyApp-nodejs'

Please note, the actual output will depend on the operating system you are using and the project name argument you pass.

Where are the env-paths docs?

The primary documentation for "env-paths" is available in its GitHub repository: https://github.com/sindresorhus/env-paths. This documentation offers detailed instructions on how to install and get started with "env-paths", along with a description of the application programming interface (API). It also provides examples of how to use the API, possible options you can use, and the output to expect.