env-paths provides OS-specific filesystem paths for common app storage needs like data, config, cache, logs, and temp files. It generates path strings based on your project name, and you can use those paths to create the directories yourself.
Project status
- Actively maintained in a limited sense, with the most recent upstream push and tag being v4.0.0 on 2026-01-24, but overall the update history is sparse since the last major version.
- Update cadence appears low, with no updates between v4.0.0 (2026-01-24) and today (2026-06-09), and a much longer gap since v3.0.0 in 2021-08-27.
AI summary generated
Recent updates
v4.0.0
Release v4.0.0 primarily upgrades the package to require Node.js 20. The code changes also introduce stricter filename safety validation for the `name` (and the appended `suffix`) used to construct paths, and update TypeScript declarations and package export metadata.
Breakingv3.0.0
v3.0.0 converts env-paths to a pure ESM package and raises the supported Node.js version. The implementation and TypeScript declaration files were updated to match ESM usage.
Breakingv2.2.1
v2.2.1 primarily updates documentation and type definition comments for env-paths by adding platform specific example locations for generated directories. It also updates the docs to clarify that the library only returns path strings and does not create directories, and modernizes the project CI configuration.
Featuresv2.2.0
v2.2.0 primarily refactors the TypeScript type definitions to be CommonJS compatible. The code diff also includes a small runtime interop change to expose a `default` property on the CommonJS export, plus test tooling updates for TypeScript definition checking.
Breakingv2.1.0
v2.1.0 primarily adds TypeScript type definitions for env-paths. The code changes are minimal and mostly focused on exporting for better interop with TypeScript/ESM tooling.
Featuresv2.0.0
This release includes a major upgrade that enforces Node.js 6 as the minimum runtime. It also changes how the library resolves the `.config` path on Windows, moving from `%LOCALAPPDATA%` to `%APPDATA%`, which affects where your configuration files are stored.
Breaking