Describe the bug
Having a base path and a prerendered root page deployed to Netlify causes the URL without a trailing slash /base-path to have broken CSS and JS links while the URL with a trailing slash /base-path/ returns the 404 page.
If the root page is not prerendered but we still have a base path, the URL without a trailing slash returns a 404 text response and the URL with a trailing slash successfully returns the root page.
I think the expected outcome is for the URL without a trailing slash to return the root page and the URL with a trailing slash to redirect to the URL without a trailing slash.
Reproduction
- Prerender the root page
src/routes/+page.svelte
- Add a base path to
svelte.config.js
- Build and deploy to Netlify using the netlify adapter
@sveltejs/adapter-netlify
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response
Describe the bug
Having a base path and a prerendered root page deployed to Netlify causes the URL without a trailing slash
/base-pathto have broken CSS and JS links while the URL with a trailing slash/base-path/returns the 404 page.If the root page is not prerendered but we still have a base path, the URL without a trailing slash returns a 404 text response and the URL with a trailing slash successfully returns the root page.
I think the expected outcome is for the URL without a trailing slash to return the root page and the URL with a trailing slash to redirect to the URL without a trailing slash.
Reproduction
src/routes/+page.sveltesvelte.config.js@sveltejs/adapter-netlifyLogs
No response
System Info
.Severity
serious, but I can work around it
Additional Information
No response