Re:Remix – A framework focused on web fundamentals and moder...
by chrisweekly on Tuesday November 23, 2021 @07:43PM
(#29325620)
> "you cannot construct a custom route on the client-side without adhering to the core concept of building your routes based on the pages directory."
Actually, that's not true. You can opt out of the fs-based routing altogether.
Re:Remix – A framework focused on web fundamentals and moder...
by micahbule on Wednesday November 24, 2021 @12:35AM
(#29327203)
I'm not aware of said functionality on the client-side. Out of curiosity, do you mind linking me to said documentation or article on how to circumvent routing on the client-side without using fs-based routing?
Re:Remix – A framework focused on web fundamentals and moder...
by chrisweekly on Wednesday November 24, 2021 @05:12PM
(#29335782)
https://nextjs.org/docs/advanced-features/custom-server#disa...
> "You may also wish to configure the client-side router to disallow client-side redirects to filename routes; for that refer to router.beforePopState."
https://nextjs.org/docs/api-reference/next/router#routerbefo...
Re:Remix – A framework focused on web fundamentals and moder...
by micahbule on Wednesday November 24, 2021 @07:30PM
(#29336914)
That is through using a custom server -- which is a whole other topic. I'm comparing apples-to-apples between NextJS's built-in router and Remix's usage of React Router as far as client-side routing is concerned.
I also agree that there's more to caching and SSG with NextJS. I'm simply stating some notable differences between NextJS and Remix, answering the top-most parent comment.