Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to Use Nextron with Dynamic Routes in Next.js 14+ App Router? #503

Open
makhdum530 opened this issue Oct 19, 2024 · 0 comments
Open

Comments

@makhdum530
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant