Critical CSS missing on every route when providing a base path when using vite env api future flag

[ColinKrist]

I'm using React Router as a...

framework

Reproduction

https://stackblitz.com/edit/github-adcvcdeh-amghqqjy?file=vite.config.ts

System Info

7.4.0 and latest nightly of /dev package because of another fix we needed around the typgen: #13267

#13066 this PR is likely related

Used Package Manager

yarn

Expected Behavior

When using vite env api future flag, I don't expect to get errors around critical css being missing.

Actual Behavior

When I provide the base in the vite config and the basename in the react config for every route I travel to I get errors saying the critical css is missing from the react router dev server package.

This only happens when using the new vite env api future flag. We're looking at adopting it early because of some issues with msw and playwright, but my repo shows that you can find this behavior in a basic case as well.

The issue seems to only affect the console output? The app seems to be working and let's me travel between routes and they look styled.

[markdalgleish]

Thanks for raising this issue!

This is fixed in #13305 which will be available in the next release.

In the meantime, you can test out this fix with the following experimental release: 0.0.0-experimental-2e661fbb4. If the fix doesn't work in your case, feel free to re-open the issue.

[ColinKrist]

I used the nightly, but yes the errors are gone! TY!!

[github-actions]

🤖 Hello there,

We just published version 7.5.0-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 7.5.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!