You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project that integrates Next.js 14+ with Electron using Nextron. However, I've encountered an issue regarding the handling of dynamic routes and the requirement for static files in production.
I understand that Electron can only handle static files when in production mode, which necessitates running next export or setting the output option to 'export' in next.config.js. This setting effectively converts my Next.js application into static HTML files.
Here are my concerns:
Dynamic Routes: I want to utilize the App Router features in Next.js 14+, which allows for dynamic routing. However, using output: 'export' seems to limit my ability to work with dynamic data that requires server-side rendering (SSR) or real-time updates.
Static Export Limitations: While I can convert some of my dynamic routes to static by implementing getStaticProps and getStaticPaths, my application relies on certain dynamic functionalities that cannot be easily converted.
Best Practices: What are the best practices for integrating Nextron with dynamic routes in Next.js? Is there a way to maintain the dynamic capabilities of my application while ensuring it can still run in an Electron environment?
The text was updated successfully, but these errors were encountered:
I'm currently working on a project that integrates Next.js 14+ with Electron using Nextron. However, I've encountered an issue regarding the handling of dynamic routes and the requirement for static files in production.
I understand that Electron can only handle static files when in production mode, which necessitates running next export or setting the output option to 'export' in next.config.js. This setting effectively converts my Next.js application into static HTML files.
Here are my concerns:
Dynamic Routes: I want to utilize the App Router features in Next.js 14+, which allows for dynamic routing. However, using output: 'export' seems to limit my ability to work with dynamic data that requires server-side rendering (SSR) or real-time updates.
Static Export Limitations: While I can convert some of my dynamic routes to static by implementing getStaticProps and getStaticPaths, my application relies on certain dynamic functionalities that cannot be easily converted.
Best Practices: What are the best practices for integrating Nextron with dynamic routes in Next.js? Is there a way to maintain the dynamic capabilities of my application while ensuring it can still run in an Electron environment?
The text was updated successfully, but these errors were encountered: