Root page with basePath doesn't work without trailingSlash
See original GitHub issueDescribe the bug
I see one problem after deploy, I have a basePath “test/dwa” and app returns 404 on:
https://d1g4p9lwi1bqdw.cloudfront.net/test/dwa
But it works on: https://d1g4p9lwi1bqdw.cloudfront.net/test/dwa/
I have trailingSlash:false
in next.js config.
sls-next/lambda-at-edge@1.6.0-alpha.5
Expected behavior Root url with subPath should work with and without trailingSlash
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Dev server does not apply base path correctly #2958 - GitHub
If I set kit.paths.base as stated in the documentation, the first page load works correctly but the import statements are relative to the...
Read more >How to obtain a path without using Link when basePath is set ...
I have a simple page in a Next.js project, under pages folder. import Link from 'next/link'; import ...
Read more >Base Path - next.config.js
basePath allows you to set a path prefix for the application. For example, to use /docs instead of / (the default), open next.config.js...
Read more >Next.js and GitHub Pages, how the basePath and assetPrefix ...
js project on GitHub Pages (without a custom domain name) your internal links won't work as your project will be hosted on a...
Read more >Host and deploy ASP.NET Core Blazor | Microsoft Learn
The app base path is the app's root URL path. Consider the following ASP. ... dotnet run --pathbase=/{RELATIVE URL PATH (no trailing slash)}....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry I wrote “subPath” but I meant “basePath” in next.config.js:
Great! Thanks!