🛣️ pathe

Universal filesystem path utils

❓ Why

For historical reasons, windows followed MS-DOS and using backslash for separating paths rather than slash used for macOS, Linux, and other Posix operating systems. Nowadays, Windows supports both Slash and Backslash for paths. Node.js's built in path module in the default operation of the path module varies based on the operating system on which a Node.js application is running. Specifically, when running on a Windows operating system, the path module will assume that Windows-style paths are being used. This makes inconsistent code behavior between Windows and POSIX. Compared to popular upath, pathe is providing identical exports of Node.js with normalization on all operations and written in modern ESM/Typescript and has no dependency on Node.js!

This package is a drop-in replacement of the Node.js's path module module and ensures paths are normalized with slash / and work in environments including Node.js.

💿 Usage

Install using npm or yarn:

1# npm
2npm i pathe
3
4# yarn
5yarn add pathe
6
7# pnpm
8pnpm i pathe

Import:

1// ESM / Typescript
2import { resolve } from 'pathe'
3
4// CommonJS
5const { resolve } = require('pathe')

Read more about path utils from Node.js documentation and rest assured behavior is ALWAYS like POSIX regardless of your input paths format and running platform!

Extra utilities

Pathe exports some extra utilities that do not exist in standard Node.js path module. In order to use them, you can import from pathe/utils subpath:

1import { filename, normalizeAliases, resolveAlias } from 'pathe/utils'

License

MIT. Made with 💖

Some code used from Node.js project. See LICENSE.