fix: decode Windows paths to prevent ENOENT in dev mode

[drewkovihair]

Fix: Decode Windows Paths in dev mode to prevent ENOENT

Summary

This fixes an error on Windows when running Hydrogen/React Router projects from folders that include spaces (e.g. D:\KOVI HAIR).

The Vite plugin currently passes encoded %20 paths into readFileSync, causing:

ENOENT: no such file or directory, open 'D:\KOVI%20HAIR\...'

Fix

We now decode routeFilePath before reading it:

const cleanPath = path.normalize(decodeURIComponent(routeFilePath));
const code = readFileSync(cleanPath, "utf-8");

Notes

• Tested with Shopify Hydrogen dev setup and confirmed working
• No impact on macOS or Linux environments
• Fixes a long-standing issue for Windows users with space-containing directories

[changeset-bot]

🦋 Changeset detected

Latest commit: e1d776d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages

Name	Type
@react-router/dev	Major
@react-router/fs-routes	Major
@react-router/remix-routes-option-adapter	Major
create-react-router	Major
react-router	Major
react-router-dom	Major
@react-router/architect	Major
@react-router/cloudflare	Major
@react-router/express	Major
@react-router/node	Major
@react-router/serve	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[remix-cla-bot]

Hi @drewkovihair,

Welcome, and thank you for contributing to React Router!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

[drewkovihair]

Let me know if anything needs adjusting — happy to tweak as needed!

[jacob-ebey]

Please commit a currently failing test with the PR and we'll get it merged. It feels like a node bug to me though due to the fact a path is being resolved with, fed through a normalization method, then failing through another method when they are all node native APIs. Node should natively handle a path resolved by, transformed by, and passed to yet another native function. Do you have a link to the "long-standing issue for Windows"? That would make me feel "better" about merging something platform specific.

[drewkovihair]

Please commit a currently failing test with the PR and we'll get it merged. It feels like a node bug to me though due to the fact a path is being resolved with, fed through a normalization method, then failing through another method when they are all node native APIs. Node should natively handle a path resolved by, transformed by, and passed to yet another native function. Do you have a link to the "long-standing issue for Windows"? That would make me feel "better" about merging something platform specific.

Added the failing test as requested!

Evidence this is a documented Windows issue:

• Stack Overflow: File System cannot find file with spaces
• Blog: "There's no %20 in file-system naming!"

Validation: Run node validate-windows-fix.js to see the fix in action.