Replies: 6 comments
-
I am facing the same issue, and don't have a solution. Have you tried doing a dynamic import the React way instead of the Next JS way? I am wondering whether this will render on the server import( |
Beta Was this translation helpful? Give feedback.
-
I just thought of another idea. Can you do the dynamic import insider getServerSideProps() like this, and then in your page you will already have a prop with the required Content object. export const getServerSideProps = async ({ params: { slug } }) => { export default Page |
Beta Was this translation helpful? Give feedback.
-
Has this issue been resolved? I'm having this same issue. |
Beta Was this translation helpful? Give feedback.
-
Having the same issue! |
Beta Was this translation helpful? Give feedback.
-
I did below. export const getServerSideProps = async ()=>{
const { getSessionTokenCookie, jwtVerify, setSessionTokenCookie } =
await import('../server/libs/authUtil');
} |
Beta Was this translation helpful? Give feedback.
-
Having similar issue. Is There any workaround or fix is available that i can try. contentData.items.map((component, index) => {
|
Beta Was this translation helpful? Give feedback.
-
Hi, I'd really appreciate some direction to solve this problem. I'd like to import a dynamic component based on props.page.type I get from getServerSideProps. My code is below:
The following code works, BUT it is not server-side rendered which is something I need:
Any ideas are greatly appreciated. Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions