Redirect ignores basePath with loading page present about next.js

[Durgaprasad-Budhwani]

I'm 100% human. Last moment they made some fixes related to base path and redirect and it has been fixed for action but it seems the issue is not fully fixed on components level.

[Durgaprasad-Budhwani]

Hey there! Ran into a bit of a snag with the redirect("/login") in your page component, huh? Especially when you're playing around with basePath in next.config.js, things can get a little tricky. I totally get the frustration when stuff just doesn't work as expected. But hey, you found a workaround by setting up a server action—that's awesome! It's all about those creative solutions.

If you're up for it, there's a video that might shed some light on the issue. Give it a watch right here: Loom Video. Sometimes, seeing it in action makes all the difference.

And if you're in the mood to dive deeper or tweak some more code, the entire codebase is waiting for you over at CodeSandbox. Who knows? You might just stumble upon something that clicks.

---

"Let's make the digital world smaller! Connect with me across the web on these social platforms and let's create, share, and inspire together." ✨🌐 #StayConnected

Solved 04

[aryobenholzner]

possibly related #59800

[SpasiboKojima]

Hey there! Ran into a bit of a snag with the redirect("/login") in your page component, huh? Especially when you're playing around with basePath in next.config.js, things can get a little tricky. I totally get the frustration when stuff just doesn't work as expected. But hey, you found a workaround by setting up a server action—that's awesome! It's all about those creative solutions.

What are you talking about? You found a workaround, if you are not a bot, then sorry, this doesn't work for me, my workaround is to sacrifice the loading.tsx component.

[SpasiboKojima]

I'm 100% human. Last moment they made some fixes related to base path and redirect and it has been fixed for action but it seems the issue is not fully fixed on components level.

Thank you for your input then, that's a valid workaround come to think of it, still hope it can be fixed on component level since it was very frustrating finding it.