wsl-utils provides JavaScript utilities for working with Windows Subsystem for Linux (WSL). It helps detect whether you are running in WSL, convert between WSL Linux paths and Windows paths, and determine Windows integration support like PowerShell accessibility and the default browser.
Project status
- The repository appears actively maintained, with multiple updates in 2025 and another on 2026-01-25, and the most recent change (v0.4.0) adds new helper functionality rather than only fixes.
- Apparent update cadence is moderately frequent in this period, with updates in 2025-05, 2025-11, and again in early 2026 (Jan 2026), suggesting an evolving pace rather than a long freeze.
AI summary generated
Recent updates
v0.4.0
v0.4.0 adds new path conversion and classification helpers, including Windows-to-WSL conversion, UNC detection, and a filesystem mapper (WSL path to Windows filesystem vs WSL filesystem). It also extends `convertWslPathToWindows` to accept an array of paths (batch conversion).
Featuresv0.3.1
v0.3.1 focuses on improving how wsl-utils parses the `root` mount point from `wsl.conf`. The code changes replace a regex-based approach with a dedicated parser intended to properly handle inline comments and quoted values.
v0.3.0
v0.3.0 adds two new exported helpers, canAccessPowerShell() and wslDefaultBrowser(), intended for Windows integration scenarios in or near WSL. It also bumps the minimum supported Node.js version to 20. The implementation changes include a refactor of the existing powerShellPath export to delegate non-WSL behavior to powershell-utils.
BreakingFeaturesv0.2.0
Release v0.2.0 adds a new utility, `convertWslPathToWindows()`, intended to translate WSL Linux paths into Windows-accessible paths. The codebase also updates TypeScript typings and the README to document the new API.
Featuresv0.1.0
Release v0.1.0 was published on 2025-05-23, but the provided release notes contain no actionable information beyond a single emoji. No changes, features, fixes, breaking changes, or migration details are described, so there is not enough documentation here to assess upgrade impact.