-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: basePath #1282
base: main
Are you sure you want to change the base?
fix: basePath #1282
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
Some other things need fixing:
|
Hi, thanks for working on it. |
I think it's out of the scope. |
OK, I will remove that when the PR is ready to merge. It's quite hard to debug without that 😭.
As this is the default behavior of Vite, I think this is more friendly to developer. Or we can talk about that in the future instead of in this PR |
Alright, then create both
Hmm, I'm not sure why it's the default behavior. How does it behave after the build? |
Vite will redirect only in dev mode as it'll be all static assets after the build. After being deployed, redirection behavior will be handled by some gateway like Nginx stuff. |
That's what I expected. So, I thought it would be better to keep the behavior the same in both DEV and PRD modes in Waku, but I don't mind following Vite's convention if that helps. |
fix: #698