# What changed in @remix-run/route-pattern

> 6 changes in @remix-run/route-pattern 0.24 to 1 from its official release notes, upgrade guides and advisories: 2 breaking. Each one cited. Sources checked 2026-10-24. HTML: https://unstale.sh/npm/@remix-run/route-pattern/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @remix-run/route-pattern 1

### Behavior and default changes

- The package reaches its first stable release. (1.0.0) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%401.0.0)

## @remix-run/route-pattern 0.25

### Breaking changes

- Generated pathnames are normalized to one leading slash, including absolute URLs and hrefs generated with baseURL; leading slashes in root wildcard values no longer round-trip unchanged. (0.25.0) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%400.25.0)
- Pathname wildcard values containing standalone `.` or `..` segments now throw CreateHrefError with details.type set to `invalid-pathname-wildcard`. (0.25.0) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%400.25.0)

### Behavior and default changes

- Package modules are declared side-effect-free, which can affect how consuming tools handle them. (0.25.0) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%400.25.0)

## @remix-run/route-pattern 0.24

### Fixes and other changes

- Rejects backslashes in hostname variables and wildcards so generated URLs retain the intended hostname. (0.24.1) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%400.24.1)
- Variable scans and capture comparisons count toward the work limit, so matching stops when optional or wildcard patterns exceed it. (0.24.1) — [release notes](https://github.com/remix-run/remix/releases/tag/route-pattern%400.24.1)