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
The dev server strips the base properly. But when I try to build, the index is rendered into a subfolder and contains a rendered error message about it being an invalid route. See this test HTML output for an index file for an example.
I discovered that this is because Route.toPath converts the Pages.Index to /sub/, but that is put into Path.fromString which chops the trailing slash, leaving /sub.
I assume there is some code somewhere that removes the base path from these paths, but since the base path is /sub/ with a trailing slash, it does not affect /sub which is left to be wrong.
The dev server strips the base properly. But when I try to build, the index is rendered into a subfolder and contains a rendered error message about it being an invalid route. See this test HTML output for an index file for an example.
Reproduction
./examples
don't build for me.)npm install
npm build -- --base sub
./dist
. There is a./dist/sub/index.html
that says "Page Not Found".The text was updated successfully, but these errors were encountered: