You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using React Router 7.0.2, deploying a prerendered app to a bucket, and serving it under a subpath, e.g., /example, using basename for the subpath.
However, when I add a loader for the root route and prerender it, the build output places an example.data file outside the /example folder, breaking the self-contained setup.
Is there a way to ensure that all build output stays within the /example folder?
reproducible by using npm create vite@latest, adding any loader to the home path and adding:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m using React Router 7.0.2, deploying a prerendered app to a bucket, and serving it under a subpath, e.g., /example, using basename for the subpath.
However, when I add a loader for the root route and prerender it, the build output places an
example.data
file outside the /example folder, breaking the self-contained setup.Is there a way to ensure that all build output stays within the /example folder?
reproducible by using
npm create vite@latest
, adding any loader to the home path and adding:to
react-router.config.ts
then:
npm run build
Beta Was this translation helpful? Give feedback.
All reactions