Replies: 1 comment
-
Okay. I believe I had fixed this issue myself. I had to redeploy my build completely. For some reason Vercel kept the same build cache and wouldn't update. If that happens, make sure you redeploy the newest build. You may have to swap branches or something. I gots my routing now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Messing around with the boilerplate, but coming into limitations with my knowledge. Since using this boilerplate, I've just learned about rewriting the directories with the reverse proxies via middleware.ts.
I know that I'm close, but I feel like I'm missing something.
In development mode, my routing works as expected. In production, the routing disappears like it never even happened.
Here is a screenshot of my routes:
I know this isn't perfect yet, but it should still work.
This is the Middleware.ts file:
As you can see I have not touched it (except modifying the "app directory", but when I try the routes in production, nothing works appropriately (except changing the primary sub-domain, that worked just fine).
The /post page displays the text "Text" as a node element. That's it.
When I go to the localhost version, on my /post page I get "test".
On localhost:
On production:
Can someone give me some insight so I can continue using this and not need to move into something else a little less complex?
Beta Was this translation helpful? Give feedback.
All reactions