normalize-path normalizes file path slashes to be posix/unix-like forward slashes, also condensing repeated slashes and removing trailing slashes by default. It is useful when you want consistent path formatting across platforms, and it is referenced as being used by tools like chokidar and anymatch.
Project status
- Maintenance status: The source appears quiet/dormant today, with no recorded updates after 3.0.0 (2018-04-19) despite an upstream push timestamp from 2022-10-07, suggesting no sustained recent release or change flow.
- Update/release cadence: Historically there were several updates in 2015 to 2018 (1.0.0 in 2015, 2.0.0 in 2015, 2.1.0 and 2.1.1 in 2017, 3.0.0 in 2018), but there has been a multi-year gap since then relative to today (2026-06-09).
AI summary generated
Recent updates
3.0.0
No release notes were provided for version 3.0.0, so the documented change list is unavailable. The code diff shows a reimplementation of the core path normalization logic (index.js), plus doc and test updates focused on Windows (win32) namespace handling and edge cases like single-slash inputs.
Features2.1.1
Release 2.1.1 updates normalize-path to a new implementation and modernizes the repository setup (docs, linting, CI config, benchmarks, and tests). The functional code change is concentrated in index.js, which now delegates trailing separator handling to a new dependency.
Breaking2.1.0
Release 2.1.0 updates the core path normalization behavior and adds a new dependency used to handle trailing separators. The provided release notes are empty, so all behavioral changes below are derived from the actual code diff and accompanying test updates.
Breaking2.0.0
Release 2.0.0 has no publisher release notes. The code diff shows a behavioral change to the exported path normalization function, plus updates to test/benchmark/documentation scaffolding.
1.0.0
Version 1.0.0 was released with no publisher-provided release notes. The code diff shows a small but important behavior change in the main `normalize-path` function, plus several documentation and dev-tooling adjustments.
v0.3.0
Release v0.3.0 was published on 2014-10-24, but no release notes were provided by the publisher. Because the notes are missing, there is no documented information here about new features, fixes, breaking changes, or dependency updates, so developers should review the repository changelog and commit history before upgrading.