Reach Router v1.3.x trailing slash handling: no built-in normalization for coexisting legacy routes

Direct answer

No. Reach Router v1.3.x has no documented community wrapper, middleware, or router option that normalizes /app and /app/ at the boundary without touching route definitions. You cannot rely on navigate or location context alone to intercept direct URL entry or server-rendered initial locations before matching occurs. For new migrations, prefer React Router v6’s useRoutes with trailingSlash over maintaining Reach Router workarounds.

Confirmed facts

• Reach Router v1.3.x ranks routes by specificity, but treats /app and /app/ as distinct path entries.
• No configuration option or built-in redirect exists in v1.3.x to reconcile trailing-slash variants across the route tree.
• The package has been in maintenance mode since 2021; its core concepts were merged into React Router v6.
• React Router v6 useRoutes supports an explicit trailingSlash option.

Likely explanation

A wrapper around navigate can strip trailing slashes for programmatic links, but it does not normalize a user typing /app/ in the address bar or the initial location during SSR. That gap must be closed at the router boundary or the server, not inside individual Route components.

Steps for this case

1. Pick one canonical form (with or without trailing slash) and apply it consistently.
2. If you control the server or CDN, add a single redirect rule that canonicalizes trailing slashes before the SPA loads.
3. If you do not control the server, add a small boundary wrapper at app mount that strips the trailing slash from location.pathname except for the root /, then pass the normalized location to Reach Router.
4. Wrap navigate calls so programmatic navigation uses the same canonical form.
5. Verify by logging location.pathname after navigating to /app and /app/; both should resolve to the same route.

Recommendation

Use the server/CDN redirect when available; it is the only fix that covers bookmarks, shared links, and SSR without client-side flash. If you are starting a new migration rather than maintaining an existing Reach Router app, adopt React Router v6 useRoutes with trailingSlash instead of investing in v1.3.x workarounds.

Missing diagnostic detail

Do you control the server or CDN in front of the application? That determines whether a single server-side redirect is sufficient or whether you need a client-side boundary wrapper.