nextron VS prerender

I believe that will mean I'll need to convert my website to using react-native-web and then use react-native-macos for the OSX app. Is that correct, or are there other options? I know Electron is an option, i.e. Nextron looks like it could do what I want.

I currently have an API running locally on my machine and a build of a Nextron app ( saltyshiomix/nextron: ⚡ Next.js + Electron ⚡ (github.com) ), I'm trying to create fetch get/post requests to the API, but I'm getting a cors error on the electron build. Everything works perfectly on the electron dev.

Side note 2: Nextron. Next.js for Electron (desktop native apps)

create-nextron-app

A second thought, I would not use create-react-app for bootstraping a project today. NextJs works pretty well and you can customize... It's even possible to use nextjs in an electron app. See https://github.com/saltyshiomix/nextron. And also prefer typescript from the start if possible.

We will use Nextron to build the desktop application. Nextron enables us to build desktop applications with Next.js. We will use TailwindCSS to help add styles to the desktop application.

So then just to experiment, I set up https://github.com/prerender/prerender on my own VPS in like an hour... and done & dusted... no more effort needed to think about SSR issues anymore. Seems great, and I can't figure out why it's not more popular.

Spending like 1 hour setting up prerender on my server is much preferable to the ongoing issues that come with having to make all my code work with SSR frameworks. And there's the added bonus that my servers don't need to waste resources doing SSR for regular human users.

Here’s an alternative that I use: https://prerender.io and GH is https://github.com/prerender/prerender

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/92.0.4512.0 Safari/537.36 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/91.0.4472.114 Safari/537.36 Prerender (+https://github.com/prerender/prerender) ...

Ah, I didn't realize this wasn't solved -- a quick search turns up:

- https://github.com/WICG/webcomponents/issues/788

- https://github.com/w3c/DOM-Parsing/issues/58

- https://github.com/w3ctag/design-reviews/issues/494

- https://web.dev/declarative-shadow-dom

In pre-render they seem to have started in this direction extremely recently:

https://github.com/prerender/prerender/pull/731/files

I don't use prerender so I can't definitively speak to it being solved and hiccup-free, but I think that limitation is going to go away in the future.

Using something like: https://github.com/prerender/prerender

Have you used prerender - https://github.com/prerender/prerender ? Seems to be doing the same thing.