solito VS nextron

I've been building for the past 3-4 months on the Solito starter repo that uses React Native to build the shared components that are used by both Next.JS for web and Expo for mobile. This theoretically should be harder/longer to build than one of these alone, but easier/shorter than building both separate projects. Has anyone built this kind of monorepo to completion/production before and can share this experience? Am I on the right path and this is a hump during the package configuration phase or would I be better off just using React and constantly maintaining two codebases that have to match feature parity?

I think this is what you are looking for: https://solito.dev/ 😊

We're encountering an issues on the web side while trying to run React Native Skia in NextJS as part of a Solito monorepo. Mobile (Expo) seems to work fine, but the "warning" Skia throws of not finding reanimated is causing Next.js builds to error out with the following error:

I’ve only just started using it but https://solito.dev/ seems to do exactly that.

I found Solito and see that it may perhaps support react-native-macos - does anyone have experience here?

It has become very practical / doable in the recent year or so. In my experience, if you have lot of frontend web experience, the easiest way to ship a RN app is by using Solito [0]. Also check out Nativewind [1] which allows you to style native apps the same way like you would on web. I was able to ship the first version of our app in about 1.5 weeks with this stack. Also checkout Tamagui [2].

[0] - https://solito.dev

Solito 4 - https://github.com/nandorojo/solito/releases/tag/v4.0.0

Another option is the Solito stack which has a single code base for react native and next js. https://solito.dev/

The [Expo docs for NextJS](https://docs.expo.dev/guides/using-nextjs/) recommends @expo/next-adapter, while I have a sense of what [Solito](https://github.com/nandorojo/solito) does as [explained by the author](https://www.youtube.com/watch?v=H1gSWXA3qfw). I'm not fully clear what the difference these two libraries are and whether they can or should be used together.

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.