Replies: 6 comments
-
Solito isn’t made for that honestly. All the web side uses Next.js, and I’m not sure it’s a necessary use case to support 2 web frameworks |
Beta Was this translation helpful? Give feedback.
-
@nandorojo thanks for your response, I totally get that! Solito and expo router is already magical, and I didn't dig deeper into them to figure out how they work exactly, but thought if it is a simple fix it may worth it. |
Beta Was this translation helpful? Give feedback.
-
i’ll think about it, since it may be possible |
Beta Was this translation helpful? Give feedback.
-
This would be awesome, as I'd like to use the simplify the navigation stack for our browser extension and could cut out our react-router-dom HashRouter. |
Beta Was this translation helpful? Give feedback.
-
Adding my voice - this would be a dream! Expo-Router + Solito 🤤 |
Beta Was this translation helpful? Give feedback.
-
If that’s your preference, there’s no real need to use Solito. The main benefit of Solito is the Next.js integration. But you can just use Expo Router on Web if you want. Solito already has an expo router example which uses it on native. The request here is mostly an escape hatch. It does feel unlikely to work, though. But we’ll see, maybe in the future. Just feels low priority |
Beta Was this translation helpful? Give feedback.
-
I created a sample app using
Everything works fine, but I started wondering if it possible to also enable the web platform in the expo app beside the ios and android platforms. I tried to enable it by adding "web" to "platforms" and configuring app.json to use the metro bundle (following the expo router documentation). This is my
app.json
:When I try to open the expo app in web it fails with an error like this:
all this around these lines in the bundle:
If this worked then I imagine we could have both a nextjs web app and an expo SPA web app using all the same components shared between nextjs and expo.
Beta Was this translation helpful? Give feedback.
All reactions